From owner-freebsd-stable@FreeBSD.ORG Sat Sep 23 11:56:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB60816A40F for ; Sat, 23 Sep 2006 11:56:48 +0000 (UTC) (envelope-from callumgibson@optusnet.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AFA043D45 for ; Sat, 23 Sep 2006 11:56:47 +0000 (GMT) (envelope-from callumgibson@optusnet.com.au) Received: from omma.gibson.athome (c220-239-41-70.rivrw7.nsw.optusnet.com.au [220.239.41.70]) by mail06.syd.optusnet.com.au (8.12.11/8.12.11) with SMTP id k8NBujka016535 for ; Sat, 23 Sep 2006 21:56:46 +1000 Received: (qmail 96920 invoked by uid 107); 23 Sep 2006 21:56:45 +1000 Date: 23 Sep 2006 21:56:45 +1000 Date: Sat, 23 Sep 2006 21:56:45 +1000 From: Callum Gibson To: freebsd-stable@freebsd.org Message-ID: <20060923115645.GA96872@omma.gibson.athome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic unloading bluetooth module X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Sep 2006 11:56:48 -0000 Hi, I just experienced a panic after playing around with bluetooth. After a fresh boot I decided to try and unload the ng_ubt module and noted all the dependencies. So I tried to unload all of them in turn a few times. Some seemed to unload but kldstat showed many of them still and it seemed like I wasn't going to be able to unload them all. Then I pressed the wlan/bluetooth toggle button and had the panic. I'm synced to 6_RELENG as at 20th September. Apparently (null) below is where "ubt" should be. There are these 2 messages, but I had many more failed attempts to unload modules which had dependencies, so perhaps they are also significant. Sep 23 21:22:35 incant kernel: kldunload: attempt to unload file that was loaded by the kernel Sep 23 21:24:16 incant kernel: kldunload: attempt to unload file that was loaded by the kernel Then here is the panic message: Sep 23 21:26:49 incant kernel: (null): at uhub0 port 2 (addr 2) disconnected Sep 23 21:26:49 incant kernel: Sep 23 21:26:49 incant kernel: Sep 23 21:26:49 incant kernel: Fatal trap 12: page fault while in kernel mode Sep 23 21:26:49 incant kernel: fault virtual address = 0x78 Sep 23 21:26:49 incant kernel: fault code = supervisor read, page not present Sep 23 21:26:49 incant kernel: instruction pointer = 0x8:0xffffffff8022e06d Sep 23 21:26:49 incant kernel: stack pointer = 0x10:0xffffffffa36c3b20 Sep 23 21:26:49 incant kernel: frame pointer = 0x10:0xffffff0000bb7d00 Sep 23 21:26:49 incant kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Sep 23 21:26:49 incant kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 23 21:26:49 incant kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Sep 23 21:26:49 incant kernel: current process = 25 (irq19: ohci0 ohci+ Sep 23 21:26:49 incant kernel: trap number = 12 Sep 23 21:26:49 incant kernel: panic: page fault -- Callum @ home http://members.optusnet.com.au/callumgibson/