From owner-freebsd-stable Wed Apr 3 16:34:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pc-62-31-80-192-ll.blueyonder.co.uk (pc-62-31-80-192-ll.blueyonder.co.uk [62.31.80.192]) by hub.freebsd.org (Postfix) with SMTP id F132B37B41A for ; Wed, 3 Apr 2002 16:34:07 -0800 (PST) Received: (qmail 186 invoked from network); 4 Apr 2002 00:34:04 -0000 Received: from spatula.home (HELO cream.org) (192.168.0.4) by myriad.home with SMTP; 4 Apr 2002 00:34:04 -0000 Message-ID: <3CAB9FC8.6030401@cream.org> Date: Thu, 04 Apr 2002 01:35:20 +0100 From: Andrew Boothman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris BeHanna Cc: FreeBSD-Stable Subject: Modules System (Was: Panic on 'kldunload snd') References: <20020403151140.T83442-100000@topperwein.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris BeHanna wrote: >>However, I was (slightly) less pleased to discover that a consequent >>'kldunload snd' paniced the kernel. This is on a (cvsuped last night) >>-STABLE box. > > Do you, perchance, have sound compiled into your kernel? There > was a bug with kldload and kldunload when loading and unloading a > module that was already compiled into the kernel, that would manifest > itself as a panic when you tried the kldunload (usually when you were > rebooting, which is how I tripped over it). No actually. I was doing this using the stock GENERIC, which contains no sound support.... I think I'm a little confused as to the current state of the kernel modules system. I mean do people out there have systems will very small kernel files and loads of *_load=YES statements in their /boot/loader.conf? This would seem to be possible, but I've never heard of anybody actually doing it. Is it just the dependancies between modules that are a bit of a problem, or is the whole system not quite ready for the light of day in a production environment? (I say this because I notice that there is no documentation on the modules system anywhere in the doc tree other than the developer's handbook.) Thanks again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message