From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 21 10:09:55 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 B0DC016A4CF for ; Wed, 21 Apr 2004 10:09:55 -0700 (PDT) Received: from smtp.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id AEB0143D5D for ; Wed, 21 Apr 2004 10:09:54 -0700 (PDT) (envelope-from neuhauser@chello.cz) Received: (qmail 77955 invoked by uid 0); 21 Apr 2004 17:09:53 -0000 Received: from r3al16.mistral.cz (HELO isis.wad.cz) (213.220.229.16) by smtp.dkm.cz with SMTP; 21 Apr 2004 17:09:53 -0000 Received: by isis.wad.cz (Postfix, from userid 1001) id 5229D2FDA01; Wed, 21 Apr 2004 19:09:53 +0200 (CEST) Date: Wed, 21 Apr 2004 19:09:52 +0200 From: Roman Neuhauser To: markm@FreeBSD.ORG Message-ID: <20040421170952.GC2088@isis.wad.cz> Mail-Followup-To: markm@FreeBSD.ORG, Kris Kennaway , freebsd-hackers References: <20040421082505.GA75715@xor.obsecurity.org> <200404211103.i3LB3aIn033981@grimreaper.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200404211103.i3LB3aIn033981@grimreaper.grondar.org> User-Agent: Mutt/1.5.6i cc: freebsd-hackers cc: Kris Kennaway 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 17:09:55 -0000 # markm@FreeBSD.ORG / 2004-04-21 12:03:36 +0100: > Kris Kennaway writes: > > > 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? > > > > I think it's expected behaviour. My fingers know what to do to stop > > this, but my brain can't remember it right now :-) > > unload > load /boot/kernel/kernel > boot > > does it for me. Of course I run unload as the first step. It wrote it unloaded the modules, and the started loading them again booting the new kernel. -- 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