From owner-freebsd-current Fri Mar 9 13:40: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E469937B719; Fri, 9 Mar 2001 13:39:58 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA23660; Fri, 9 Mar 2001 13:40:01 -0800 Date: Fri, 9 Mar 2001 13:39:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: current@FreeBSD.org, Mark Murray Subject: Re: Entropy harvesting? Grim reaper is more like it... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Mar 2001, John Baldwin wrote: > > On 09-Mar-01 Matthew Jacob wrote: > > On Fri, 9 Mar 2001, Mark Murray wrote: > > > >> > I changed nothing from whatever the default is. It seems like a bit of > >> > POLA to > >> > freeze now. > >> > > >> > But I'll check this - if I can get that machine up again :-)... > >> > >> OK - if this is the entropy driver, then typing about 2 lines of shit > >> will unlock it. > > > > Neither ^T or typing does anything. I'll have to do some surgery from another > > boot disk to find out what's what. Uk. > > Erm, just so you know. The 4100 here at WC doesn't even make it past the SCSI > probe due to interrupt issues. If it's running really up to date current, > try changing sys/alpha/include/mutex.h to define mtx_intr_enable() to nothing, > which will hackishly run ithreads with a raised IPL and might solve the problem > if its an interrupt storm you are seeing. Hmm. Well, it *was* working a couple of days ago :-).... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message