From dgilbert@daveg.ca Wed Feb 25 06:41:19 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8436C16A4CE for ; Wed, 25 Feb 2004 06:41:19 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DE6443D31 for ; Wed, 25 Feb 2004 06:41:19 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 9BCE62FE0B; Wed, 25 Feb 2004 09:41:18 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 039D21D26F1; Wed, 25 Feb 2004 08:52:35 -0500 (EST) Message-Id: <20040225135235.039D21D26F1@canoe.dclg.ca> Date: Wed, 25 Feb 2004 08:52:35 -0500 (EST) From: David Gilbert Reply-To: David Gilbert To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: ums doesn't detatch completely? Reattach panics. X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 63351 >Category: kern >Synopsis: ums doesn't detatch completely? Reattach panics. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 25 06:50:01 PST 2004 >Closed-Date: Fri Sep 03 17:04:05 GMT 2004 >Last-Modified: Fri Sep 03 17:04:05 GMT 2004 >Originator: David Gilbert >Release: FreeBSD 5.2-CURRENT i386 >Organization: DaveG.ca >Environment: System: FreeBSD canoe.dclg.ca 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Mon Feb 23 19:57:40 EST 2004 dgilbert@canoe.dclg.ca:/usr/obj/usr/src/sys/CANOE i386 cvsup and world in the last 24 hours. >Description: This behaviour is fairly recent. I have a laptop with an internal psm0 device and several USB ports. At home, I have one mouse plugged into one usb port. For travelling on the train, I have another mouse and due to the geometry of the situation, I plug it into another usb port. When I leave the house, I unplug the house mouse, and close the laptop ... note that it doesn't suspend. I've set the acpi lid_button to "NONE" ... meaning it doesn't even try. when I get on the train, I open the laptop and plug in the train mouse. As soon as this tries to attach, I get the included panic. This is recent behaviour ... but I'm not positive how recent. Within the last couple of weeks, I beleive. Here's the data from the crash dump: panic: make_dev() by driver ums on pre-existing device (maj=0, min=0, name=console) at line 492 in file /usr/src/sys/kern/kern_conf.c (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0xc0516b31 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:374 #2 0xc0516dcc in poweroff_wait (junk=0xc067c6ea, howto=492) at /usr/src/sys/kern/kern_shutdown.c:552 #3 0xc04fc200 in make_dev (devsw=0xc1e81540, minornr=-543685724, uid=0, gid=0, perms=0, fmt=0xc0674ec4 "ums%d") at /usr/src/sys/kern/kern_conf.c:490 #4 0xc04d87ee in ums_attach (self=0xc6b4f880) at /usr/src/sys/dev/usb/ums.c:356 #5 0xc0529f05 in device_probe_and_attach (dev=0xc6b4f880) at device_if.h:39 #6 0xc04dc0ed in usbd_probe_and_attach (parent=0xc5dea800, dev=0xc6a98800, port=2, addr=2) at /usr/src/sys/dev/usb/usb_subr.c:900 #7 0xc04dc4cb in usbd_new_device (parent=0xc5dea800, bus=0xc5df5000, depth=0, speed=1, port=2, up=0xc5dea7c0) at /usr/src/sys/dev/usb/usb_subr.c:1114 #8 0xc04d4325 in uhub_explore (dev=0xc5dea900) at /usr/src/sys/dev/usb/uhub.c:480 #9 0xc04da91f in usb_discover (v=0xc5dde940) at /usr/src/sys/dev/usb/usb.c:717 #10 0xc04da416 in usb_event_thread (arg=0xc5dde940) at /usr/src/sys/dev/usb/usb.c:410 #11 0xc0506b48 in fork_exit (callout=0xc04da3cc , arg=0xc5dde940, frame=0xdf980d48) at /usr/src/sys/kern/kern_fork.c:802 >How-To-Repeat: As above. >Fix: None. >Release-Note: >Audit-Trail: From: David Gilbert To: freebsd-gnats-submit@FreeBSD.org, dgilbert@daveg.ca Cc: Subject: Re: kern/63351: ums doesn't detatch completely? Reattach panics. Date: Wed, 25 Feb 2004 10:09:24 -0500 More details: when I detach the train mouse, the following dmesg ensues: ums0: at uhub1 port 2 (addr 2) disconnected ums0: detached When I plug the train mouse back in (this time staring at the console rather than X), the panic messages occur immediately without any attach messages being printed. Let me know if turning on some debug would help diagnose, but I fear that this is rather easy to reproduce. From: David Gilbert To: freebsd-gnats-submit@FreeBSD.org, dgilbert@daveg.ca Cc: Subject: Re: kern/63351: ums doesn't detatch completely? Reattach panics. Date: Wed, 03 Mar 2004 21:48:50 -0500 Hrnh. It appears that -CURRENT as of today (at least) no longer exhibits this feature. State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Fri Sep 3 17:03:43 GMT 2004 State-Changed-Why: Submitter can no longer duplicate the problem and agrees PR should be closed. http://www.freebsd.org/cgi/query-pr.cgi?pr=63351 >Unformatted: