Bug 25582
Summary: | xhci_hcd not working: xHCI xhci_drop_endpoint called with disabled ep ffff88021048f300 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Ivan (infinity.probability) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | a92zu, arno, infinity.probability |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.38.1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Ivan
2010-12-23 22:02:34 UTC
Kernel: 2.6.37 from kernel.org on top of Debian Lenny I have a similar problem with the combination of a Sharkoon USB3.0 controller (NEC 720200) and a Western Digital My Book Essential Edition 3TB, USB3.0 drive (I have no other USB3.0 devices at this time). The controller is basically unusable under Linux as it is. It works fine with win7 though. I get disconnects, failure to detect (sometimes on one port, while the other port works!), failure to detect when connected to an USB3 hub, detection as USB2.0, etc.. Sometimes it works for all these scenarios. I have two of these controllers (at current firmware 3.0.2.7), two of the drives, 3 UBS3.0 cables and tested this in two different computers. All show the same behavior, so defective hardware is out. Sometime it even works flawlessly for a time, for example, I could do a full overwrite of the 3TB drive without problems and at USB3.0 speeds last night. When I then tried to create an ext4 filesystem, I got the disconnect given as first log excerpt below. Both disks work fine when connected to an USB2.0 port. Some sample log entries: -------- Disconnect during operation: Jan 30 03:01:55 gatewagner kernel: xhci_hcd 0000:03:00.0: WARN: transfer error on endpoint Jan 30 03:01:55 gatewagner kernel: usb 8-1: reset SuperSpeed USB device using xhci_hcd and address 4 Jan 30 03:01:55 gatewagner kernel: xhci_hcd 0000:03:00.0: WARN: short transfer on control ep Jan 30 03:01:55 gatewagner kernel: xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep f659acec Jan 30 03:01:55 gatewagner kernel: xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep f659acc0 --------- Warning on successful detect: Jan 29 14:16:39 gatewagner kernel: usb 8-1: new SuperSpeed USB device using xhci _hcd and address 4 Jan 29 14:16:39 gatewagner kernel: xhci_hcd 0000:03:00.0: WARN: short transfer o n control ep -------- Failed detection: Jan 24 16:46:55 gatewagner kernel: usb 8-3: new high speed USB device using xhci_hcd and address 2 Jan 24 16:46:56 gatewagner kernel: usb 8-3: Device not responding to set address. Jan 24 16:46:56 gatewagner kernel: usb 8-3: Device not responding to set address. Jan 24 16:46:56 gatewagner kernel: usb 8-3: device not accepting address 2, error -71 Jan 24 16:46:56 gatewagner kernel: hub 8-0:1.0: unable to enumerate USB device on port 3 ------- lspci for the controller: ~$lspci -v -s 2:0.0 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: Intel Corporation Gigabit CT Desktop Adapter Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fbde0000 (32-bit, non-prefetchable) [size=128K] Memory at fbd00000 (32-bit, non-prefetchable) [size=512K] I/O ports at dc00 [size=32] Memory at fbddc000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at fbd80000 [disabled] [size=256K] Capabilities: <access denied> Kernel driver in use: e1000e ------- lsusb for the disk drive Bus 001 Device 002: ID 1058:1130 Western Digital Technologies, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x1130 bcdDevice 10.12 iManufacturer 1 Western Digital iProduct 2 My Book 1130 iSerial 3 574341575A30313530323332 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0003 Self Powered Remote Wakeup Enabled Wups, wrong device in lspci. Here is the correct one: ------ 03:00.0 USB Controller: NEC Corporation Device 0194 (rev 03) (prog-if 30) Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at fbefe000 (64-bit, non-prefetchable) [size=8K] Capabilities: [50] Power Management version 3 Capabilities: [70] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable- Capabilities: [90] MSI-X: Enable+ Mask- TabSize=8 Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff Capabilities: [150] #18 Kernel driver in use: xhci_hcd Hi there, The kernel got updated to 2.6.38.1, but this is still happening. Any news? The Microsoft Nano for the mouse is probably the culprit, but how can be sure? Thanks I don't quite follow. The box I first observed this on is a headless server that does not have a mouse or keyboard. There is nothing Microsoft on that computer that I know of. Is anybody investigating this problem? Are there any tests to run in order to help with the investigation? Dunno. I think that the problem maybe related directly to the USB 3.0 stack. For me is the mouse that's triggering the problem. Here are some dmesg lines just after plugging the said mouse: ++++++++++++++ [ 7.705369] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.0/input/input10 [ 7.705467] generic-usb 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® Nano Transceiver v1.0] on usb-0000:05:00.0-3/input0 [ 7.715339] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.1/input/input11 [ 7.715426] generic-usb 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® Nano Transceiver v1.0] on usb-0000:05:00.0-3/input1 [ 7.726973] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.729965] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.732968] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.735948] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.739940] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.742943] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.745974] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.748972] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.752005] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.754975] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.757954] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.760968] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.763949] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.766959] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 7.768165] input: Microsoft Microsoft® Nano Transceiver v1.0 as /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.2/input/input12 ++++++++++++ When it fails, it does without any kind of warning or output message. Removing _two times_ both xhci_hcd and ehci_hcd, disconnecting the mouse, and connecting again, makes it work for at least 5 min. Thanks Ah, I see. I think this is the USB3.0 Stack. The only thing I ever connected were the USB3.0 HDDs from WD and an USB3.0 hub, with the erratic results I reported. Arno On Tue, Apr 12, 2011 at 08:26:58PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=25582 > > > > > > --- Comment #5 from Ivan <infinity.probability@gmail.com> 2011-04-12 > 20:26:53 --- > Dunno. I think that the problem maybe related directly to the USB 3.0 stack. > For me is the mouse that's triggering the problem. Here are some dmesg lines > just after plugging the said mouse: > > ++++++++++++++ > > [ 7.705369] input: Microsoft Microsoft?? Nano Transceiver v1.0 as > /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.0/input/input10 > [ 7.705467] generic-usb 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 > Keyboard [Microsoft Microsoft?? Nano Transceiver v1.0] on > usb-0000:05:00.0-3/input0 > [ 7.715339] input: Microsoft Microsoft?? Nano Transceiver v1.0 as > /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.1/input/input11 > [ 7.715426] generic-usb 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 > Mouse [Microsoft Microsoft?? Nano Transceiver v1.0] on > usb-0000:05:00.0-3/input1 > [ 7.726973] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.729965] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.732968] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.735948] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.739940] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.742943] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.745974] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.748972] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.752005] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.754975] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.757954] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.760968] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.763949] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.766959] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep > [ 7.768165] input: Microsoft Microsoft?? Nano Transceiver v1.0 as > /devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb3/3-3/3-3:1.2/input/input12 > > ++++++++++++ > > When it fails, it does without any kind of warning or output message. > Removing > _two times_ both xhci_hcd and ehci_hcd, disconnecting the mouse, and > connecting > again, makes it work for at least 5 min. > > Thanks > > -- > Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. Not sure, but it seems this has improved with 2.6.38.4. Today I tried again to do backups to my UDB3.0 disks and completely failed with 2.6.38.2. Could not even get a clean, error-free detection when directly attached to USB3.0 ports. Checking on kernel.org I saw some xHCI fixes in 3.6.38.4 and tried that with exactly the same config file. Two rather large backups (~400GB) then went through at USB3.0 speeds. Of course, this is not a conclusive tests, but something seems to have improved. No idea about the USB3.0 hubs, though. The update actually made things worse for me. Now I'm getting +++++++++++++++++++ [ 1504.767051] usb 3-3: new full speed USB device using xhci_hcd and address 2 [ 1504.794566] xhci_hcd 0000:05:00.0: WARN: Stalled endpoint [ 1504.796574] xhci_hcd 0000:05:00.0: WARN: Stalled endpoint [ 1504.798573] xhci_hcd 0000:05:00.0: WARN: Stalled endpoint [ 1504.807561] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 1504.811569] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 1504.814545] xhci_hcd 0000:05:00.0: WARN: short transfer on control ep [ 1504.815500] usb 3-3: New USB device found, idVendor=045e, idProduct=0745 [ 1504.815507] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1504.815512] usb 3-3: Product: Microsoft® Nano Transceiver v1.0 [ 1504.815516] usb 3-3: Manufacturer: Microsoft [ 1504.815858] xhci_hcd 0000:05:00.0: ERROR: unexpected command completion code 0x11. [ 1504.815868] usb 3-3: can't set config #1, error -22 +++++++++++++++++++ And the mouse doesn't work at all. Gonna try 2.6.39-rc4 and see if things improve. 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. |