Bug 7113
| Summary: | USB Mass storage devices are detected and then die | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Brad (brad7) |
| Component: | USB | Assignee: | Alan Stern (stern) |
| Status: | REJECTED INVALID | ||
| Severity: | normal | CC: | bunk, greg, stern |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | Linux 2.6.17.11 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5089 | ||
|
Description
Brad
2006-09-05 20:13:43 UTC
It's possible that the problem lies in your USB device or in your computer's USB controller. The log messages make it look like a problem in the device, but they could be deceptive. Once the mass-storage device disconnects, what happens if you rmmod uhci-hcd and then modprobe it back? Reply-To: brad@k1gto.com I don't think it's device specific. I've tried two different USB memory drives, and an external IDE enclosure. These devices all work fine on my other computer in windows. Here is a snippet from my syslog as I unplugged both devices, rmmod, modprobe, then plugged just the 256MB thumb-drive back in. http://old.k1gto.com/wiki/index.php/Kernel_toubleshooting I tried to do some troubleshooting by loading old kernels (2.6.0, 2.6.5, 2.6.10), but the old kernels won't compile so I've abandoned that idea. I would have to "downgrade" GCC and some other stuff by the looks of it. -----Original Message----- From: bugme-daemon@bugzilla.kernel.org [mailto:bugme-daemon@bugzilla.kernel.org] Sent: Wednesday, September 06, 2006 10:14 AM To: brad7@k1gto.com Subject: [Bug 7113] USB Mass storage devices are detected and then die http://bugzilla.kernel.org/show_bug.cgi?id=7113 stern@rowland.harvard.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stern@rowland.harvard.edu ------- Additional Comments From stern@rowland.harvard.edu 2006-09-06 07:05 ------- It's possible that the problem lies in your USB device or in your computer's USB controller. The log messages make it look like a problem in the device, but they could be deceptive. Once the mass-storage device disconnects, what happens if you rmmod uhci-hcd and then modprobe it back? ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. Please don't include the original message text when replying by email. It just clutters up the bug report. It's possible that the problem lies elsewhere in your computer, such as in the interrupt controller. Here's how you can get more information. First, make sure that CONFIG_USB_DEBUG and CONFIG_DEBUG_FS are both set in your kernel. Next, after the problem occurs type: mount -t debugfs none /sys/kernel/debug rmmod uhci-hcd modprobe uhci-hcd debug=2 Plug in the thumb-drive and then -- here the timing is important -- while the system is trying and failing to initialize the thumb-drive, make a copy of /sys/kernel/debug/uhci/0000:00:07.3 (the last part of the path is the PCI address of the controller into which you plug the drive). Maybe even make several copies while the initialization is going on, just to be sure nothing gets missed. It also would be a good idea to make copies of /proc/interrupts before and after plugging in the thumb-drive, to see if the interrupt count goes up. Reply-To: brad@k1gto.com Lots of debug detail this time. Nothing jumped out at me as obviously wrong, but then again I don't really understand all the low-level messages. I organized all the information in my wiki at the following URL: http://old.k1gto.com/wiki/index.php/Info_for_kernel_bug It includes the /proc/interrupts before and after, syslog output, and the debugfs file. Note that I wrote a script to grab the contents of the debugfs file any time it changed and piped it to stdout. You'll see what I mean when you click the link - it should be pretty straight forward. The UHCI debugging output indicates that the USB controller is broken. There's no way to know whether it's actually sending any data over the USB bus, but it definitely is not updating the data in the computer's memory. Apparently it's not a permanent problem; the controller starts out working after a power reset and then stops. By the way, this doesn't mean the EHCI controller is also broken. It could be that if you plugged in a high-speed USB device, it would work just fine. Do the other USB ports behave the same way? If they do, your only option is to buy an add-on PCI USB card. Connected PCI USB card, connected thumb drive to it, mounted thumb drive, performed tests, all tests passed without incident - Problem is with onboard USB hardware as stated by Alan. No bug. I'm closing call with resolution of "invalid". |