From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 21 01:25:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7EFC16A4CE; Wed, 21 Apr 2004 01:25:06 -0700 (PDT) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CB6443D3F; Wed, 21 Apr 2004 01:25:06 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (45580ed925f661040ef1621d9e7fb155@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i3L8NspT007286; Wed, 21 Apr 2004 01:23:55 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7A75353097; Wed, 21 Apr 2004 01:25:05 -0700 (PDT) Date: Wed, 21 Apr 2004 01:25:05 -0700 From: Kris Kennaway To: Kris Kennaway , freebsd-hackers , markm@freebsd.org Message-ID: <20040421082505.GA75715@xor.obsecurity.org> References: <20040405003553.GG27087@isis.wad.cz> <20040405020207.GA44906@xor.obsecurity.org> <20040421082013.GA650@isis.wad.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20040421082013.GA650@isis.wad.cz> User-Agent: Mutt/1.4.2.1i Subject: Re: panic: random.ko X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 08:25:06 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 21, 2004 at 10:20:14AM +0200, Roman Neuhauser wrote: > # 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=3DYES in > > > loader.conf causes a panic very similar to the one described here: > > > http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.h= tml > > >=20 > > > "Hi Mark, please fix random.ko" :-) > >=20 > > Sounds like a generic module problem that is known to exist on > > FreeBSD. "Don't do that" is the solution. > >=20 > > You can unload the preloaded kernel and/or modules from the loader to > > prevent it from panicking at boot, then modify loader.conf. >=20 > 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 > =20 > load > boot >=20 > or >=20 > boot >=20 > 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? I think it's expected behaviour. My fingers know what to do to stop this, but my brain can't remember it right now :-) Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAhi/eWry0BWjoQKURAkT8AJ0Xet03/Dh+fND/+V5fToGeYJKRwQCeIjHs uHNP7laDmXqJwCg40BMD6Qc= =Uqfw -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--