From owner-freebsd-current@FreeBSD.ORG Mon Apr 12 02:40:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB24116A4CE; Mon, 12 Apr 2004 02:40:56 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D02E43D45; Mon, 12 Apr 2004 02:40:51 -0700 (PDT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i3C9eoV4048423; Mon, 12 Apr 2004 10:40:50 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i3C9eoUp048422; Mon, 12 Apr 2004 10:40:50 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i3C9ZcIn084537; Mon, 12 Apr 2004 10:35:38 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200404120935.i3C9ZcIn084537@grimreaper.grondar.org> To: "Simon L. Nielsen" In-Reply-To: Your message of "Mon, 12 Apr 2004 10:59:55 +0200." <20040412085955.GB798@zaphod.nitro.dk> Date: Mon, 12 Apr 2004 10:35:37 +0100 Sender: mark@grondar.org X-Spam-Score: 4 (****) FROM_NO_LOWER,MSGID_FROM_MTA_SHORT X-Scanned-By: MIMEDefang 2.39 X-Mailman-Approved-At: Mon, 12 Apr 2004 04:47:22 -0700 cc: freebsd-current@FreeBSD.ORG cc: Mark Murray Subject: Re: random(4) related panic: sleeping without a mutex X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2004 09:40:57 -0000 "Simon L. Nielsen" writes: > > Could you please try the enclosed patch? > > It fixes the panic, but now it just hangs after init. Fix panic is good (fix committed). Hang is bad. :-( > I tried to boot both my working kernel (Apr 4) and the new one in single > user mode. The sysctl output for kern.random looks interesting since > the old one was seeded, and the new one isn't: You aren't harvesting any entropy; any reason for that? > kern.random.sys.harvest.ethernet: 0 > kern.random.sys.harvest.point_to_point: 0 > kern.random.sys.harvest.interrupt: 0 > kern.random.sys.harvest.swi: 0 > Since it doesn't harvest I guess it's not that strange that it isn't > seeded, but since it worked before something must have changed. Yeah. Part of the startup does a "kickstart" of the device by writing garbage to it. I wonder why it didn't do that this time. Is your /etc/rc* completely up to date? What is in your rc.conf? M -- Mark Murray iumop ap!sdn w,I idlaH