From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 21 01:20:17 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 2691516A4CE for ; Wed, 21 Apr 2004 01:20:17 -0700 (PDT) Received: from smtp.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id D5A0543D49 for ; Wed, 21 Apr 2004 01:20:15 -0700 (PDT) (envelope-from neuhauser@chello.cz) Received: (qmail 75227 invoked by uid 0); 21 Apr 2004 08:20:14 -0000 Received: from r3al16.mistral.cz (HELO isis.wad.cz) (213.220.229.16) by smtp.dkm.cz with SMTP; 21 Apr 2004 08:20:14 -0000 Received: by isis.wad.cz (Postfix, from userid 1001) id 2525D2FDA01; Wed, 21 Apr 2004 10:20:14 +0200 (CEST) Date: Wed, 21 Apr 2004 10:20:14 +0200 From: Roman Neuhauser To: Kris Kennaway Message-ID: <20040421082013.GA650@isis.wad.cz> Mail-Followup-To: Kris Kennaway , freebsd-hackers , markm@freebsd.org References: <20040405003553.GG27087@isis.wad.cz> <20040405020207.GA44906@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040405020207.GA44906@xor.obsecurity.org> User-Agent: Mutt/1.5.6i cc: freebsd-hackers 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:20:17 -0000 # 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 boot or boot 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