From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 21 04:05:22 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 B066E16A4CF for ; Wed, 21 Apr 2004 04:05:22 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87E4C43D55 for ; Wed, 21 Apr 2004 04:05:19 -0700 (PDT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i3LB5IHB038310; Wed, 21 Apr 2004 12:05:18 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i3LB5IVA038309; Wed, 21 Apr 2004 12:05:18 +0100 (BST) (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i3LB3aIn033981; Wed, 21 Apr 2004 12:03:37 +0100 (BST) (envelope-from mark@grondar.org) Message-Id: <200404211103.i3LB3aIn033981@grimreaper.grondar.org> To: Kris Kennaway From: markm@FreeBSD.ORG In-Reply-To: Your message of "Wed, 21 Apr 2004 01:25:05 PDT." <20040421082505.GA75715@xor.obsecurity.org> Date: Wed, 21 Apr 2004 12:03:36 +0100 Sender: mark@grondar.org X-Spam-Score: 3.339 (***) MSGID_FROM_MTA_SHORT,NO_REAL_NAME X-Scanned-By: MIMEDefang 2.39 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 11:05:22 -0000 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. M -- Mark Murray iumop ap!sdn w,I idlaH