From owner-freebsd-stable Tue Apr 2 18:58:42 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 7779637B41B for ; Tue, 2 Apr 2002 18:58:38 -0800 (PST) Received: (qmail 157 invoked from network); 3 Apr 2002 02:58:35 -0000 Received: from spatula.home (HELO cream.org) (192.168.0.4) by myriad.home with SMTP; 3 Apr 2002 02:58:35 -0000 Message-ID: <3CAA7026.8010409@cream.org> Date: Wed, 03 Apr 2002 03:59:50 +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: stable@FreeBSD.org Subject: Panic on 'kldunload snd' 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 Hi Folks! I just started playing with all those modules that are compiled during buildkernel, and was very pleased to see my SoundBlaster AWE64 correctly probed and configured when I did a 'kldload snd'. 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. I did a bit of a dig around in the PR database and also in the mailing list archives and I _think_ this type of thing is a known problem with the modules system. If this is the case, apologies for the waste of bandwith, but I thought I had better mention it. If anyone is interested however, I do have dump from the panic. Which is good actually because I had enabled crash dumps, but -stable has been so bloody stable I'd never had a dump to play with in kgdb before :-) Thanks Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message