From owner-freebsd-current@FreeBSD.ORG Thu Sep 16 21:46:14 2004 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 90D7616A4CE for ; Thu, 16 Sep 2004 21:46:14 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4928143D3F for ; Thu, 16 Sep 2004 21:46:14 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 61635C520; Thu, 16 Sep 2004 17:46:13 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id EF96C1D2C21; Thu, 16 Sep 2004 17:46:10 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16714.2466.353010.629983@canoe.dclg.ca> Date: Thu, 16 Sep 2004 17:46:10 -0400 To: freebsd-current@freebsd.org X-Mailer: VM 7.17 under 21.5 (beta17) "chayote" (+CVS-20040321) XEmacs Lucid Subject: usb hub disconnect crashes 5.3-BETA4 hard 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: Thu, 16 Sep 2004 21:46:14 -0000 I have two different USB mice. One is a little portable one that has a wireless "dongle" that pluggs into the port. This one works fine. The second is an MX-900 (Logitec) that is a "bluetooth" mouse... but the unit itself shows up as a USB hub and a usb mouse in that hub. This (I believe) is due to the fact that the "base station" is emulating a usb mouse ... but also has the ability to show up as a bluetooth receiver (if you enable it). That function is not enabled on my mouse --- so it shows up as hub with a mouse attached to the hub. When the hub/mouse is unplugged, FreeBSD-5.3-BETA4 panic's hard but BETA2 did not. This may be a false hope ... I think I have seen this before, but I don't remember exactly. When it panics hard, I see "ums0 detached" (bright text) followed by "(null) at uhub4 " followed by a panic message an no dump. Here is the kernel messages for the working mouse: [3:2:302]dgilbert@canoe:~> dmesg | grep -i usb uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhci1: port 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhci2: port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 ehci0: mem 0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 ums0: PATEN USB Receiver, rev 1.10/1.03, addr 2, iclass 3/1 ums0: PATEN USB Receiver, rev 1.10/1.03, addr 2, iclass 3/1 Here are the kernel messages for the mouse attaching (obviously I can't show the exact detatch messages): uhub4: Texas Instruments General Purpose USB Hub, class 9/0, rev 1.10/1.01, addr 3 uhub4: 2 ports with 0 removable, bus powered ums1: Logitech USB Receiver, rev 1.10/27.04, addr 4, iclass 3/1 ums1: 7 buttons and Z dir. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================