From owner-freebsd-current@FreeBSD.ORG Wed Dec 10 14:45:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F1016A4CE for ; Wed, 10 Dec 2003 14:45:12 -0800 (PST) Received: from mta6-svc.business.ntl.com (mta6-svc.business.ntl.com [62.253.164.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEBD343D2A for ; Wed, 10 Dec 2003 14:45:06 -0800 (PST) (envelope-from bruce@cran.org.uk) Received: from buffy.brucec.backnet ([81.107.236.234]) by mta6-svc.business.ntl.comESMTP <20031210224505.KINN12753.mta6-svc.business.ntl.com@buffy.brucec.backnet>; Wed, 10 Dec 2003 22:45:05 +0000 Received: from buffy.brucec.backnet (localhost.brucec.backnet [127.0.0.1]) hBAMiDLF001180; Wed, 10 Dec 2003 22:44:13 GMT (envelope-from bruce@buffy.brucec.backnet) Received: (from bruce@localhost) by buffy.brucec.backnet (8.12.10/8.12.10/Submit) id hBAMiCju001179; Wed, 10 Dec 2003 22:44:12 GMT (envelope-from bruce) Date: Wed, 10 Dec 2003 22:44:12 +0000 From: Bruce Cran To: Jay Cornwall Message-ID: <20031210224412.GA1066@buffy.brucec.backnet> References: <1069874342.704.18.camel@klotz.local> <1070218984.675.4.camel@klotz.local> <3FCCE217.2090302@evilrealms.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FCCE217.2090302@evilrealms.net> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: Panic with ugen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 22:45:13 -0000 On Tue, Dec 02, 2003 at 07:03:51PM +0000, Jay Cornwall wrote: > Martin wrote: > > >>Could you try the attached patch (rm -f sys/dev/usb/ugen.c, cvs up > >>sys/dev/usb/ugen.c, patch ...) to see if it alleviates the panic? It > >>should at least give a more specific panic, if it doesn't fix the problem. > > >Sorry for the delay, I got a busy weekend. > > And sorry for the delay here too. Had a busy start-of-week. :\ > > >I still got a panic after starting the small piece of code, but it looks > >like this now: > > > >fatal trap 12 > >fault virtual address = 0x5 > >supervisor read, page not present > >[...] > > > >trace shows me "ugen_set_config()" at top of the stack. > > Hmm. I'm afraid I'm not really sure why my patch doesn't fix the problem. > > Unfortunately, to fix this I think I'd need to be able to reproduce the > panic locally and do some debugging. Otherwise, I'd just be guessing at > what's causing the problem. > > If you could provide a full backtrace with a debug-enabled kernel > ('makeoptions DEBUG=-g' in your kernel configuration file, with GDB using > kernel.debug to obtain symbols - I think onlamp.com had a tutorial on doing > this) I may be able to locate where things are going wrong. But if it's too > much hassle for you, I think it'd be best to pass this on to a developer > with a machine to test the panic on. > > Thanks for trying the patches, though. :) I've just had the same panic on -CURRENT: ugen0: at uhub1 port 1 (addr 2) disconnected^M WARNING: Driver mistake: destroy_dev on 114/1^M panic: don't do that^M Debugger("panic")^M db> tr^M Debugger(c05eb534) at Debugger+0x45^M panic(c05e8a79,c05e8aac,72,1,1) at panic+0xbb^M destroy_dev(c47f3b00,2,c4852860,e9b25c84,c47ff53d) at destroy_dev+0x32^M ugen_destroy_devnodes(c4851000,c47f3900,c4851000,c484f100,c484f100) at ugen_destroy_devnodes+0x5b^M ugen_detach(c484f100) at ugen_detach+0xc1^M device_detach(c484f100) at device_detach+0x56^M device_delete_child(c47b4980,c484f100,c482661e,2,c43e9240) at device_delete_child+0x31^M usb_disconnect_port(c47b4730,c47b4980,3,c43e9270,c47b4708) at usb_disconnect_port+0x90^M uhub_explore(c47fc600,c43ee9e0,e9b25d1c,c4812372,c43ee9e0) at uhub_explore+0x144^M usb_discover(c43ee9e0,c4812328,e9b25d34,c04ab904,c43ee9e0) at usb_discover+0x2f^M usb_event_thread(c43ee9e0,e9b25d48,c43ee9e0,c4812328,0) at usb_event_thread+0x4a^M fork_exit(c4812328,c43ee9e0,e9b25d48) at fork_exit+0x90^M fork_trampoline() at fork_trampoline+0x8^M This was after trying to get my Speedtouch USB modem working - I kldloaded ugen, ran and stopped the ppp daemon which runs pppoa2 a few times, and then unplugged the modem. It's an EHCI usb port. I've got a full crash dump, but I don't know what to do with it since it lists the 'dumping++' line of kern_shutdown, not the actual panic code. If there's anything there of any use, I'll keep the vmcore file. uname "FreeBSD buffy.brucec.backnet 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Dec 10 21:12:15 GMT 2003 root@:/usr/obj/usr/src/sys/MYKERNEL i386" -- Bruce Cran