Arch Linux

hussam

Member

Registered: 2006-03-26

Posts: 572

Website

[solved] USB disk issue.

I have a usb disk disconnect issue that only happens once after every reboot and with only one device.

261859.758934] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
[261859.790850] usb-storage 2-3:1.0: USB Mass Storage device detected
[261859.808931] scsi host4: usb-storage 2-3:1.0
[261860.889869] scsi 4:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
[261860.900690] sd 4:0:0:0: [sdc] 60555264 512-byte logical blocks: (31.0 GB/28.9 GiB)
[261860.902351] sd 4:0:0:0: [sdc] Write Protect is off
[261860.902353] sd 4:0:0:0: [sdc] Mode Sense: 45 00 00 00
[261860.902863] sd 4:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[261861.203006]  sdc: sdc1
[261861.206710] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[261870.675435] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[270392.450023] sdc: detected capacity change from 31004295168 to 0
[270525.833136] xhci_hcd 0000:00:14.0: Cannot set link state.
[270525.833139] usb usb2-port3: cannot disable (err = -32)
[270525.833144] usb 2-3: USB disconnect, device number 2

So far since last reboot a few days ago, I've used the same usb disk over 20 times and the 'cannot disable' error only happened the first time.
I've also test 5 other usb disks on the same port and none showed this issue.
However, the 5 other usb disks are 2.0 while the troublesome one is 3.0.
shouldn't 3.0 devices be backwards compatible with 2.0 ports?

The output of lsusb with only mouse and keyboard attached:

 lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 1a2c:0c23 China Resource Semico Co., Ltd 
Bus 001 Device 002: ID 0581:0101 Racal Data Group 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Note: I've tested for the last month or so after rebooting for kernel updates. This really does only happens once after reboots.

Edit: A recent kernel update fixed it. (somewhere between 4.9.56 and 4.9.59)

Last edited by hussam (2017-11-03 18:23:09)