Hi
On 14.03.2017 18:16, Nathan Shearer wrote:
I have been archiving data from old hard drives, and I have a drive that
spins up, but does not finish detecting (the drive is faulty). When this
happens on kernel 4.10.1 there is some kind of a timeout, and the usb
port that my dock is plugged into is permanently disabled until I
reboot. Disconnecting the usb dock and power cycling the dock does not
fix the usb port. Below is my kernel messages log when I power up the dock:
Does earlier kernels work better? 4.10 has a change in USB 3 port disabling
which is also called when usb core fails to address a device.
37be6676 usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
Older kernels would re-enable usb3 ports immediately after port disable.
Does dock work in other ports after power cycle?
does disabled port react to other USB devices?
Mar 14 09:51:38 varws03 kernel: usb 4-4: new SuperSpeed USB device
number 26 using xhci_hcd
Mar 14 09:51:38 varws03 kernel: usb 4-4: New USB device found,
idVendor=0480, idProduct=a006
Mar 14 09:51:38 varws03 kernel: usb 4-4: New USB device strings: Mfr=2,
Product=3, SerialNumber=1
Mar 14 09:51:38 varws03 kernel: usb 4-4: Product: ASM1351
Mar 14 09:51:38 varws03 kernel: usb 4-4: Manufacturer: Asmedia
Mar 14 09:51:38 varws03 kernel: usb 4-4: SerialNumber: 123456789116
Mar 14 09:51:38 varws03 kernel: scsi host6: uas
Mar 14 09:51:38 varws03 kernel: scsi 6:0:0:0: Direct-Access ASMT
2135 0 PQ: 0 ANSI: 6
Mar 14 09:51:39 varws03 kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Mar 14 09:51:39 varws03 kernel: sd 6:0:0:0: [sdb] Spinning up disk...
Mar 14 09:51:41 varws03 kernel: .
Mar 14 09:51:42 varws03 kernel: .
Mar 14 09:51:43 varws03 kernel: .
Mar 14 09:51:44 varws03 kernel: .
Mar 14 09:51:45 varws03 kernel: .
Mar 14 09:51:45 varws03 kernel: .
Mar 14 09:51:45 varws03 kernel: ready
Mar 14 09:52:15 varws03 kernel: sd 6:0:0:0: tag#0 uas_eh_abort_handler 0
uas-tag 1 inflight: CMD IN
Mar 14 09:52:15 varws03 kernel: sd 6:0:0:0: tag#0 CDB: Read capacity(16)
9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00
Mar 14 09:52:15 varws03 kernel: scsi host6: uas_eh_bus_reset_handler start
Mar 14 09:52:20 varws03 kernel: xhci_hcd 0000:00:14.0: WARN: unexpected
TRB Type 4
This shouldn't be unexpected, it's a status stage of a control transfer.
This means a control transfer was stopped at the status stage, either because
the command timed out, or URB was canceled (killed, dequeued) by class driver.
I'm guessing timeout as it's 5 seconds since last log entry.
Mar 14 09:52:20 varws03 kernel: usb 4-4: Disable of device-initiated U1
failed.
Mar 14 09:52:26 varws03 kernel: xhci_hcd 0000:00:14.0: WARN: unexpected
TRB Type 4
Mar 14 09:52:26 varws03 kernel: usb 4-4: Disable of device-initiated U2
failed.
Mar 14 09:52:31 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:52:37 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:52:37 varws03 kernel: usb 4-4: device not accepting address
26, error -62
Mar 14 09:52:42 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:52:48 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:52:48 varws03 kernel: usb 4-4: device not accepting address
26, error -62
Mar 14 09:52:54 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:52:59 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:53:00 varws03 kernel: usb 4-4: device not accepting address
26, error -62
Mar 14 09:53:05 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:53:11 varws03 kernel: xhci_hcd 0000:00:14.0: Timeout while
waiting for setup device command
Mar 14 09:53:11 varws03 kernel: usb 4-4: device not accepting address
26, error -62
Mar 14 09:53:11 varws03 kernel: scsi host6: uas_post_reset: alloc
streams error -19 after reset
Mar 14 09:53:11 varws03 kernel: usb 4-4: USB disconnect, device number 26
Is this a kernel bug? Should I report it here or at
https://bugzilla.kernel.org/ ?
here is fine, but bugzilla could be useful to keep logs and patches etc in as well.
Can you take logs with xhci debugging enabled? Actully both traces and debug messages:
before plugging in the dock:
echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
echo xhci-hcd >> /sys/kernel/debug/tracing/set_event
Then send both the output of dmesg and /sys/kernel/debug/tracing/trace
-Mathias
--
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
