Bug 35212
Summary: | USB 3.0 controller on Clevo P150HM dies on reconnect | ||
---|---|---|---|
Product: | Drivers | Reporter: | Julian Sikorski (belegdol) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | yelena_volynets |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.38.6-26.rc1.fc15.x86_64 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | Test case for Bug 35212: USB 3.0 controller: re-connection problem |
Description
Julian Sikorski
2011-05-16 18:58:26 UTC
Upon resume the controller seems to be completely dead, not producing any logs upon device plugged in. It is still a problem with 3.0. Moreover, the ports would sometimes die with machine on: Aug 10 21:52:03 snowball2 kernel: [10822.659308] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint Aug 10 21:52:03 snowball2 kernel: [10822.660149] sd 6:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor] Aug 10 21:52:03 snowball2 kernel: [10822.660153] Descriptor sense data with sense descriptors (in hex): Aug 10 21:52:03 snowball2 kernel: [10822.660154] 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 09 9d Aug 10 21:52:03 snowball2 kernel: [10822.660159] 00 0c 00 7d 40 50 Aug 10 21:52:03 snowball2 kernel: [10822.660162] sd 6:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d Aug 10 21:52:03 snowball2 kernel: [10822.660499] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint Aug 10 21:52:03 snowball2 kernel: [10822.745535] xhci_hcd 0000:02:00.0: WARN: Stalled endpoint Aug 10 21:52:15 snowball2 kernel: [10835.221438] xhci_hcd 0000:02:00.0: xHCI host not responding to stop endpoint command. Aug 10 21:52:15 snowball2 kernel: [10835.221451] xhci_hcd 0000:02:00.0: Assuming host is dying, halting host. Aug 10 21:52:15 snowball2 kernel: [10835.228925] xhci_hcd 0000:02:00.0: HC died; cleaning up Aug 10 21:52:15 snowball2 kernel: [10835.228965] usb 4-2: USB disconnect, device number 2 Aug 10 21:52:15 snowball2 kernel: [10835.229049] sd 6:0:0:0: Device offlined - not ready after error recovery Aug 10 21:52:15 snowball2 kernel: [10835.229089] sd 6:0:0:0: rejecting I/O to offline device Aug 10 21:52:15 snowball2 kernel: [10835.229121] sd 6:0:0:0: rejecting I/O to offline device Aug 10 21:52:15 snowball2 kernel: [10835.229146] Buffer I/O error on device dm-3, logical block 19816543 Aug 10 21:52:15 snowball2 kernel: [10835.229151] Buffer I/O error on device dm-3, logical block 19816544 Aug 10 21:52:15 snowball2 kernel: [10835.229156] Buffer I/O error on device dm-3, logical block 19816545 Aug 10 21:52:15 snowball2 kernel: [10835.229160] Buffer I/O error on device dm-3, logical block 19816546 Aug 10 21:52:15 snowball2 kernel: [10835.229163] Buffer I/O error on device dm-3, logical block 19816547 Aug 10 21:52:15 snowball2 kernel: [10835.229167] Buffer I/O error on device dm-3, logical block 19816548 Aug 10 21:52:15 snowball2 kernel: [10835.229171] Buffer I/O error on device dm-3, logical block 19816549 Aug 10 21:52:15 snowball2 kernel: [10835.229174] Buffer I/O error on device dm-3, logical block 19816550 Aug 10 21:52:15 snowball2 kernel: [10835.229178] Buffer I/O error on device dm-3, logical block 19816551 Aug 10 21:52:15 snowball2 kernel: [10835.229249] sd 6:0:0:0: [sdb] Unhandled error code Aug 10 21:52:15 snowball2 kernel: [10835.229251] sd 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Aug 10 21:52:15 snowball2 kernel: [10835.229254] sd 6:0:0:0: [sdb] CDB: Read(10): 28 00 09 7d 0c 9e 00 00 f0 00 Aug 10 21:52:15 snowball2 kernel: [10835.229262] end_request: I/O error, dev sdb, sector 159190174 Created attachment 68452 [details] Test case for Bug 35212: USB 3.0 controller: re-connection problem Test case for Bug 35212: USB 3.0 controller: re-connection problem. I had a problem similar to this Bug 35212 using kernel 2.6.39 and Seagate 2.5” USB3 external drives. They cannot re-connect. I installed a new kernel 3.0. The behavior is somewhat better: I can reconnect 2.5” USB 3 drives now, but I still can break it, if I disconnect USB3 drive very quickly, before it was recognizes by the system, then it cannot connect the second time. Please note: if I use 3.5” USB3 external drive with its own power supply, the problem does not happen, even on a very fast disconnect. I did try it with ACPI Support ON and OFF, but it did not affect 2.5” USB3 reconnection problem. It is very easy to create the problem by simply wiggling the connector during the insertion, and then not seeing the device at all, so it is important to fix. Please note: after breaking it with 2.5” USB3 drive, I cannot connect 3.5” USB3 drive either. USB2 does not have this problem on any of the above units no matter how fast I connect and disconnect them. I tested with different USB3 cards with the same result. I installed Kernel 3.0.3, but my quick re-connection problem with Seagate USB3 unit (PID=2332) is still the same Aug 19 11:53:03 JblUsbEr70 kernel: [83105.812037] xhci_hcd 0000:34:00.0: Timeout while waiting for a slot Aug 19 11:53:23 JblUsbEr70 kernel: [83126.016046] xhci_hcd 0000:34:00.0: Timeout while waiting for a slot Aug 19 11:53:23 JblUsbEr70 kernel: [83126.220033] usb 17-1: device not accepting address 6, error -62 Aug 19 11:53:43 JblUsbEr70 kernel: [83146.220035] xhci_hcd 0000:34:00.0: Timeout while waiting for a slot Aug 19 11:53:43 JblUsbEr70 kernel: [83146.220044] hub 17-0:1.0: couldn't allocate port 1 usb_device All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. |