Date: Tue, 4 Mar 2003 04:21:14 -0700 From: "Cliff L. Biffle" <cbiffle@safety.net> To: current@freebsd.org Subject: USB port periodically dies, now with complete body text Message-ID: <200303040421.14971.cbiffle@safety.net>
next in thread | raw e-mail | index | archive | help
Damn KMail. Full text to follow: --- I've been having a reliable USB issue on my 5-current box (3 Mar, 23:58:25 MST). It's been happening since I upgraded to -current in the DP2 days, and has happened on two completely independent motherboards. On the more recent of the two (the previous died) I've enabled USB_DEBUG. Here's the deal. The port periodically dies. Once it dies, a reboot clears it up every time, but nothing short of that will. Once one port has died, any device plugged into another port causes it to quit working as well. (I generally have only my mouse plugged in.) During normal use with hw.usb.ums.debug, hw.usb.uhub.debug, and hw.usb.debug set to 1, I get a lot of lines like: ums_intr: status=13 When the port finally dies, it does so with no fanfare; the mouse simply stops responding. If I unplug the mouse, I get: uhub_explore: C_PORT_ENABLED uhub_explore: device addr=2 disappeared on port 2 ums0: at uhub0 port 1 (addr 2) disconnected ums0: disconnected ums0: detached uhub_explore: get port status failed, error=TIMEOUT uhub_explore: get port status failed, error=TIMEOUT uhub_explore: get port status failed, error=TIMEOUT If I reconnect the mouse: uhub_explore: C_PORT_ENABLED uhub0: port error, restarting port 1 usbd_new_device bus=0xc261b000 port=1 depth=1 speed=1 usbd_new_device: addr=2, getting first desc failed usbd_remove_device: 0xc2e68a00 uhub_explore: usb_new_device failed, error=TIMEOUT uhub0: device problem, disabling port 1 uhub_explore: get port status failed, error=TIMEOUT [last line repeats every few seconds] ...and disconnect: uhub_explore: C_PORT_ENABLED uhub0: port error, restarting port 1 uhub_explore: status change hub=1 port=1 ...and then the same stuff as above. Repeat ad nauseum The ports work fine under Linux. The earlier motherboard I saw this on worked fine under 4-stable; I have not yet had an opportunity to nuke my machine and install 4.7. :-) (Though I will say that I have very, very similar symptoms on my 4.7 OHCI-based laptop, though it does it starting right from boot, instead of working for a while and then going insane. Again, ports work fine under Linux. I suspect it may be unrelated.) What should I instrument? Any debug flags I can turn on? -Cliff L. Biffle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303040421.14971.cbiffle>