Hello,
I own a JBOD SATA<->USB 3.0 bridge. All information about this device
and my kernel version is below.
My trouble is that every so often this device will undergo a virtual
USB disconnect and then be reconnected. This will cause all drives to
disappear and reappear on the system. All previously mounted file
systems will have to be remounted.
Here is the relevant dmesg upon initially plugging in the device:
[400295.378851] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
[400295.396512] usb 2-3: New USB device found, idVendor=152d, idProduct=0567
[400295.396524] usb 2-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
[400295.396531] usb 2-3: Product: USB to ATA/ATAPI Bridge
[400295.396537] usb 2-3: Manufacturer: JMicron
[400295.396542] usb 2-3: SerialNumber: 152D00539000
[400295.398121] usb-storage 2-3:1.0: USB Mass Storage device detected
[400295.402320] usb-storage 2-3:1.0: Quirks match for vid 152d pid 0567: 5000000
[400295.402399] scsi host4: usb-storage 2-3:1.0
[400296.401394] scsi 4:0:0:0: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
[400296.402428] scsi 4:0:0:1: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
[400296.403322] scsi 4:0:0:2: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
[400296.404113] scsi 4:0:0:3: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
[400296.404920] scsi 4:0:0:4: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
[400296.405762] scsi 4:0:0:5: Direct-Access ST2000DL 004 HD204UI 0125 PQ: 0 ANSI: 6
[400296.406576] scsi 4:0:0:6: Direct-Access WL1000GS A6472 0125 PQ: 0 ANSI: 6
Here is the relevant dmesg when the device disconnects:
[383320.013453] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[383337.784897] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[387835.464685] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[387835.753168] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[387835.953264] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[387898.688906] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[387898.852856] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388019.498978] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388019.743249] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388020.019291] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388020.307342] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388050.608983] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388050.752992] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388071.128536] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388071.428820] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388071.692850] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[388072.016931] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[389815.300165] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[389815.616611] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[389815.816690] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[394497.291005] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[394497.531051] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[394498.015147] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[395273.727018] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[395274.267090] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[395341.903233] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[396598.497860] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[399452.105930] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 3 ep 2 with no TDs queued?
[399821.971271] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[399955.972112] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[399956.184142] usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
[400266.037316] usb 2-3: Device not responding to setup address.
[400266.244922] usb 2-3: Device not responding to setup address.
[400266.445391] usb 2-3: device not accepting address 2, error -71
[400270.434213] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[400274.422951] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[400278.411675] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[400278.412144] usb 2-3: USB disconnect, device number 2
Afterward the device connects again.
Another user of this same hardware claims that this happens when the
bridge encounters a faulty (or slow-to-respond) HDD. When the HDD is
slow to respond, the bridge resets
itself. (http://forum.mediasonic.ca/viewtopic.php?f=58&t=3115#p13119)
Initially I accepted this explanation but now I am starting to
question it. For one, all of my HDDs seem to be in good shape
according to their S.M.A.R.T. attributes and S.M.A.R.T. self-checks.
Another thing that looks fishy to me are the excessive "reset"
messages in dmesg. Looks like sometimes the reset works and sometimes
it doesn't. There are many reset attempts in this specific dmesg but
in previous resets there could be as few as one.
My current guess is some kind of spurious error is happening in
usb_stor_invoke_transport(), causing a call to usb_stor_port_reset(),
usb_reset_device(), usb_reset_and_verify_device(), and ultimately
hub_port_init(), which is causing the "reset" message. My guess
is that the kernel is timing out on a USB command to the device,
invoking a reset, and then timing out on a successful reset since the
device may still be busy doing something else.
Is this possible? Does the USB stack call reset on a command timeout?
Is there a way to increase such a timeout?
Additionally, I'm not sure what the "WARN" line means.
Here are my system details:
My uname -a:
Linux doma 4.3.0-1-amd64 #1 SMP Debian 4.3.5-1 (2016-02-06) x86_64 GNU/Linux
I know this isn't the latest kernel but I've had this problem on
multiple previous kernels and on multiple host machines for the past
two years. I highly doubt the latest kernel solves this issue.
Here is the consumer product:
http://www.mediasonic.ca/product.php?id=1357290761
lsusb -v gives me:
Bus 002 Device 003: ID 152d:0567 JMicron Technology Corp. / JMicron USA
Technology Corp. JMS567 SATA 6Gb/s bridge
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x152d JMicron Technology Corp. / JMicron USA
Technology Corp.
idProduct 0x0567 JMS567 SATA 6Gb/s bridge
bcdDevice 2.05
iManufacturer 10
iProduct 11
iSerial 5
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 44
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-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
I'm not on the list so please CC me with all responses.
Thanks,
Rian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
