Date: Sun, 4 Apr 2004 19:02:07 -0700 From: Kris Kennaway <kris@obsecurity.org> To: freebsd-hackers <freebsd-hackers@freebsd.org>, markm@freebsd.org Subject: Re: panic: random.ko Message-ID: <20040405020207.GA44906@xor.obsecurity.org> In-Reply-To: <20040405003553.GG27087@isis.wad.cz> References: <20040405003553.GG27087@isis.wad.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: > Booting a kernel with random compiled in, and load_random=3DYES in > loader.conf causes a panic very similar to the one described here: > http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html >=20 > "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. Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAcL4fWry0BWjoQKURAmI8AJ9ALVVV4VodoCYXAfdApXbz6zxWpQCfapvX FpHyHQ2eIGyTZup61hodTZ0= =2ctw -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040405020207.GA44906>