From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 4 19:02:10 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 5137B16A4CE; Sun, 4 Apr 2004 19:02:10 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 405A543D1D; Sun, 4 Apr 2004 19:02:10 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (c7c4ccc97540fa614c0a847c180280f4@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i35228qW008038; Sun, 4 Apr 2004 19:02:08 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E51A051C12; Sun, 4 Apr 2004 19:02:07 -0700 (PDT) Date: Sun, 4 Apr 2004 19:02:07 -0700 From: Kris Kennaway To: freebsd-hackers , markm@freebsd.org Message-ID: <20040405020207.GA44906@xor.obsecurity.org> References: <20040405003553.GG27087@isis.wad.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <20040405003553.GG27087@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: Mon, 05 Apr 2004 02:02:10 -0000 --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--