Date: Mon, 12 Apr 2004 23:19:59 +0100 From: Mark Murray <markm@FreeBSD.ORG> To: "Simon L. Nielsen" <simon@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: random(4) related panic: sleeping without a mutex Message-ID: <200404122219.i3CMJxIn091105@grimreaper.grondar.org> In-Reply-To: Your message of "Mon, 12 Apr 2004 20:25:18 %2B0200." <20040412182518.GB797@zaphod.nitro.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
"Simon L. Nielsen" writes: > > 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? > > The problem is that I use initdiskless which is run as the very first > rc.d script, even before initrandom. It has to run first since /etc is > replaced by that script. Hmmm. Methinks initdiskless should depend on initrandom. > As a workaround I added the hack from initrandom (ps -fauxww; sysctl... > >/dev/random and so on) and the system boots again. So I'm not really > sure if this should be fixed in rc.d or in the kernel. Short term; rc.d. Long term, kernel might not be a bad idea. There are some very nasty initial conditions to fix first. The device MUST start up secure, for one. > Is it intentional that random(4) isn't seeded by the kernel itself now? Unintentional, but hard to fix. M -- Mark Murray iumop ap!sdn w,I idlaH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404122219.i3CMJxIn091105>