Date: Wed, 21 Apr 2004 10:20:14 +0200 From: Roman Neuhauser <neuhauser@chello.cz> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: panic: random.ko Message-ID: <20040421082013.GA650@isis.wad.cz> In-Reply-To: <20040405020207.GA44906@xor.obsecurity.org> References: <20040405003553.GG27087@isis.wad.cz> <20040405020207.GA44906@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
# kris@obsecurity.org / 2004-04-04 19:02:07 -0700: > On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: > > Booting a kernel with random compiled in, and load_random=YES in > > loader.conf causes a panic very similar to the one described here: > > http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html > > > > "Hi Mark, please fix random.ko" :-) > > Sounds like a generic module problem that is known to exist on > FreeBSD. "Don't do that" is the solution. > > You can unload the preloaded kernel and/or modules from the loader to > prevent it from panicking at boot, then modify loader.conf. The fun part (and reason I asked whether there was a way to tell loader to ignore loader.con) was that "unload" didn't help, it showed the kernel and modules were unloaded, but subsequent load <kernel> boot or boot <kernel> loaded the the modules again, and I had to "disable-module" for every individual module, about twelve times. Is that normal behavior, or was there a pilot error somewhere? -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040421082013.GA650>