174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled

[linux4me]

I have a 1 TB Western Digital drive in a USB 3.0 HDD dock that will not automount with Ubuntu 13.10 while XHCI is enabled in the BIOS. If I disable XHCI in the BIOS, it automounts normally. I've tried an external USB 3.0 enclosure and two different brands of USB 3.0 HDD docks (that use different chipsets) with the 1 TB drive and it still will not automount. Dmesg shows the following when the drive is turned on:
[10813.786820] usb 4-5.3: new SuperSpeed USB device number 4 using xhci_hcd
[10823.816236] usb 4-5.3: New USB device found, idVendor=174c, idProduct=5106
[10823.816245] usb 4-5.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[10823.816250] usb 4-5.3: Product: AS2105
[10823.816255] usb 4-5.3: Manufacturer: ASMedia
[10828.823853] usb 4-5.3: can't set config #1, error -110

WORKAROUND: Disable XHCI in the BIOS, but this runs at USB 2.0 speeds using EHCI.

I actually thought the 1 TB drive was bad, and I RMA'd it to Western Digital, but the replacement drive fails with the same error message. I have a couple of Western Digital 500 GB drives that work just fine in the same HDD dock with XHCI enabled. All the drives were formatted in Ubuntu 13.10 using LUKS via the Disks Utility. I have tried various settings in the BIOS (XHCI set at Smart Auto, Auto, and Manual) but they make no difference. I found an old bug report with the same "can't set config #1, error -110" error message that recommended adding "pci=nomsi" to Grub, but that did not work either.

Upstream URL: permalink.gmane.org/gmane.linux.usb.general/101979

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jsherman 2017 F.... pulseaudio
 /dev/snd/controlC0: jsherman 2017 F.... pulseaudio
 /dev/snd/pcmC0D1p: jsherman 2017 F...m pulseaudio
CurrentDmesg:
 [ 81.782320] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
 [ 81.782396] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 81.782532] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 85.304006] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
 [ 85.304039] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Tue Jan 21 09:43:25 2014
HibernationDevice: RESUME=UUID=ea044d07-2ac1-43ee-8d34-3b5df6559f94
InstallationDate: Installed on 2013-12-16 (35 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87X-UD3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z87X-UD3H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/

[Brad Figg (brad-figg)]

This change was made by a bot.

[linux4me (ta2008)]

I tested with upstream kernel v. 3.13.0-031300 and the problem persists.

[penalvch (penalvch)]

linux4me, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[linux4me (ta2008)]

I've collected the information described for an upstream bug report and am ready to email it, but I'm not sure where it should go.

The page you gave me, https://wiki.ubuntu.com/Bugs/Upstream/kernel, separates submissions into USB bugs and non-USB bugs. This seems like a USB bug of the non-wireless type, but the addresses listed are for "USB dongles," and this isn't a dongle issue.

So do I submit it to <email address hidden> as I would for a non-wireless USB dongle issue, or to a particular driver maintainer?

[penalvch (penalvch)]

linux4me, as per http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS given the problem would be related to xhci_hcd, I would send it to the linux-usb mailinglist, CC Sarah Sharp <email address hidden> .

[linux4me (ta2008)]

Thanks Christopher. I have emailed it as you suggested. I'll add the link to the email in the mailing list here when I receive it.

[linux4me (ta2008)]

Here's the link to the upstream report: http://permalink.gmane.org/gmane.linux.usb.general/101979

[Joschibrauchle (joschibrauchle)]

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36

Hi,

I have an external USB3 harddrive attached to an USB3 port on my desktop PC running openSUSE 13.1.

At random times, sometimes multiple times a minute, the USB3 device gets disconnected. It does not matter if the device is mounted (in use) or not.

Please see dmesg output:
----------------------------
[870461.269481] usb 4-3: new SuperSpeed USB device number 28 using xhci_hcd
[870461.281358] usb 4-3: New USB device found, idVendor=174c, idProduct=55aa
[870461.281372] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[870461.281374] usb 4-3: Product: USB 3.0 Device
[870461.281376] usb 4-3: Manufacturer: Intenso
[870461.281378] usb 4-3: SerialNumber: 31800000000000003E38
[870461.282007] usb-storage 4-3:1.0: USB Mass Storage device detected
[870461.282089] usb-storage 4-3:1.0: Quirks match for vid 174c pid 55aa: 400000
[870461.282167] scsi36 : usb-storage 4-3:1.0
[870462.284210] scsi 36:0:0:0: Direct-Access Intenso USB 3.0 Device 0 PQ: 0 ANSI: 6
[870462.284401] sd 36:0:0:0: Attached scsi generic sg6 type 0
[870464.199577] sd 36:0:0:0: [sdf] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[870464.199581] sd 36:0:0:0: [sdf] 4096-byte physical blocks
[870464.199874] sd 36:0:0:0: [sdf] Write Protect is off
[870464.199877] sd 36:0:0:0: [sdf] Mode Sense: 43 00 00 00
[870464.200155] sd 36:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[870464.221691] sdf: sdf1 sdf2 sdf3
[870464.222938] sd 36:0:0:0: [sdf] Attached SCSI disk
[870549.477048] usb 4-3: USB disconnect, device number 28
[870549.538986] sd 36:0:0:0: [sdf] Synchronizing SCSI cache
[870549.539025] sd 36:0:0:0: [sdf]
[870549.539028] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[870549.539211] usb 4-3: Set SEL for device-initiated U1 failed.
[870549.539214] usb 4-3: Set SEL for device-initiated U2 failed.
[870549.745153] usb 4-3: new SuperSpeed USB device number 29 using xhci_hcd
[870549.756736] usb 4-3: New USB device found, idVendor=174c, idProduct=55aa
[870549.756743] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[870549.756746] usb 4-3: Product: USB 3.0 Device
[870549.756748] usb 4-3: Manufacturer: Intenso
[870549.756751] usb 4-3: SerialNumber: 31800000000000003E38
[870549.757361] usb-storage 4-3:1.0: USB Mass Storage device detected
[870549.757408] usb-storage 4-3:1.0: Quirks match for vid 174c pid 55aa: 400000
[870549.757443] scsi37 : usb-storage 4-3:1.0
[870550.758808] scsi 37:0:0:0: Direct-Access Intenso USB 3.0 Device 0 PQ: 0 ANSI: 6
[870550.758971] sd 37:0:0:0: Attached scsi generic sg6 type 0
[870550.759173] sd 37:0:0:0: [sdf] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[870550.759175] sd 37:0:0:0: [sdf] 4096-byte physical blocks
[870550.759432] sd 37:0:0:0: [sdf] Write Protect is off
[870550.759434] sd 37:0:0:0: [sdf] Mode Sense: 43 00 00 00
[870550.760176] sd 37:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[870550.798929] sdf: sdf1 sdf2 sdf3
[870550.799953] sd 37:0:0:0: [sdf] Attached SCSI disk
[870566...

[Tiwai-r (tiwai-r)]

Oliver, another git for you.

[Oneukum (oneukum)]

Looks like you might need 140e3026a57ab7d830dab2f2c57796c222db0ea9
This issue affects only some HCDs. Please provide the output of "lspci -vvvk"

[Graymark (graymark)]

I added my address to the CC: list because something similar happens to me. I
have two 4GB seagate USB3 "desktop expansion drives" which change device (say
from sdc to sdd) if they are being written to _very_ slowly (an image copy of
my mostly zeroed Win8 partition compressed by xz for instance). Otherwise they
behave perfectly well - never as much as a burp. My approach to my problem is
"don't do that then" so I have not bothered to report the bug (and like I said
my bug is only _slightly_ similar -- apart from complaining that the drive it
was writing to has "disappeared" the kernel does not log any other errors.) My
drives never "disconnect" when not not being used, or when read or written to
at "normal" (very fast!) speeds. (Just my 2 cents worth -- I didn't want to
distract attention from this rather different bug by mentioning this before.)

[Joschibrauchle (joschibrauchle)]

Created an attachment (id=581976)
Output of 'lspci -vvvk'

[Oneukum (oneukum)]

Please try the test kernel at
https://build.opensuse.org/project/monitor?project=home%3Aoneukum%3Abnc864866a

[Oneukum (oneukum)]

(In reply to comment #4)
> Created an attachment (id=581976) [details]
> Output of 'lspci -vvvk'

This is not the affected HCD. So it may be:
http://comments.gmane.org/gmane.linux.usb.general/101512
The test kernel includes the proposed, untested patch.

[Joschibrauchle (joschibrauchle)]

Unfortunately the test kernel does not fix the bug, see:

----------------------
[ 89.544267] usb 4-3: USB disconnect, device number 2
[ 89.544898] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
[ 89.544956] sd 6:0:0:0: [sdb]
[ 89.544958] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 89.545052] usb 4-3: Set SEL for device-initiated U1 failed.
[ 89.545053] usb 4-3: Set SEL for device-initiated U2 failed.
[ 92.965861] usb 4-3: new SuperSpeed USB device number 3 using xhci_hcd
[ 92.977711] usb 4-3: New USB device found, idVendor=174c, idProduct=55aa
[ 92.977716] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 92.977729] usb 4-3: Product: USB 3.0 Device
[ 92.977731] usb 4-3: Manufacturer: Intenso
[ 92.977733] usb 4-3: SerialNumber: 31800000000000003E38
[ 92.978349] usb-storage 4-3:1.0: USB Mass Storage device detected
[ 92.978435] usb-storage 4-3:1.0: Quirks match for vid 174c pid 55aa: 400000
[ 92.978481] scsi9 : usb-storage 4-3:1.0
[ 93.981618] scsi 9:0:0:0: Direct-Access Intenso USB 3.0 Device 0 PQ: 0 ANSI: 6
[ 93.981793] sd 9:0:0:0: Attached scsi generic sg2 type 0
[ 95.233545] sd 9:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 95.233548] sd 9:0:0:0: [sdb] 4096-byte physical blocks
[ 95.233853] sd 9:0:0:0: [sdb] Write Protect is off
[ 95.233857] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 95.234134] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 95.247774] sdb: sdb1 sdb2 sdb3
[ 95.249078] sd 9:0:0:0: [sdb] Attached SCSI disk
[ 295.886411] usb 4-3: USB disconnect, device number 3
[ 295.886939] sd 9:0:0:0: [sdb] Synchronizing SCSI cache
[ 295.887031] sd 9:0:0:0: [sdb]
[ 295.887034] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 295.887138] usb 4-3: Set SEL for device-initiated U1 failed.
[ 295.887140] usb 4-3: Set SEL for device-initiated U2 failed.
[ 296.092510] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[ 296.103979] usb 4-3: New USB device found, idVendor=174c, idProduct=55aa
[ 296.103981] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 296.103983] usb 4-3: Product: USB 3.0 Device
[ 296.103984] usb 4-3: Manufacturer: Intenso
[ 296.103986] usb 4-3: SerialNumber: 31800000000000003E38
[ 296.104600] usb-storage 4-3:1.0: USB Mass Storage device detected
[ 296.104652] usb-storage 4-3:1.0: Quirks match for vid 174c pid 55aa: 400000
[ 296.104680] scsi10 : usb-storage 4-3:1.0
[ 297.107297] scsi 10:0:0:0: Direct-Access Intenso USB 3.0 Device 0 PQ: 0 ANSI: 6
[ 297.107654] sd 10:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 297.107656] sd 10:0:0:0: [sdb] 4096-byte physical blocks
[ 297.107786] sd 10:0:0:0: Attached scsi generic sg2 type 0
[ 297.107917] sd 10:0:0:0: [sdb] Write Protect is off
[ 297.107928] sd 10:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 297.108172] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 297.109296] sdb: sdb1 sdb2 sdb3
[ 297.110307] sd 10:0:0:0: [sdb] Attached SCSI disk
st-brauchle:/home/brauchle # uname -a
Linux st-brauchle 3.11.10-1.g17f...

[Oneukum (oneukum)]

Please provide the log from the moment of first plug in onwards

[Joschibrauchle (joschibrauchle)]

Which log do you mean exactly? dmesg output?
Is there anything I can do to provide a more verbose log?

[Joschibrauchle (joschibrauchle)]

This is dmesg from the initial plug in:

[ 110.249771] usb 4-4: new SuperSpeed USB device number 2 using xhci_hcd
[ 110.261313] usb 4-4: New USB device found, idVendor=174c, idProduct=55aa
[ 110.261318] usb 4-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 110.261322] usb 4-4: Product: USB 3.0 Device
[ 110.261325] usb 4-4: Manufacturer: Intenso
[ 110.261328] usb 4-4: SerialNumber: 31800000000000003E38
[ 110.261980] usb-storage 4-4:1.0: USB Mass Storage device detected
[ 110.262020] usb-storage 4-4:1.0: Quirks match for vid 174c pid 55aa: 400000
[ 110.262039] scsi8 : usb-storage 4-4:1.0
[ 111.264363] scsi 8:0:0:0: Direct-Access Intenso USB 3.0 Device 0 PQ: 0 ANSI: 6
[ 111.264513] sd 8:0:0:0: Attached scsi generic sg7 type 0
[ 113.180356] sd 8:0:0:0: [sdg] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 113.180359] sd 8:0:0:0: [sdg] 4096-byte physical blocks
[ 113.180661] sd 8:0:0:0: [sdg] Write Protect is off
[ 113.180664] sd 8:0:0:0: [sdg] Mode Sense: 43 00 00 00
[ 113.180910] sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 113.201961] sdg: sdg1 sdg2 sdg3
[ 113.202944] sd 8:0:0:0: [sdg] Attached SCSI disk

[Joschibrauchle (joschibrauchle)]

This from the first actual unplug event:

[ 469.850589] usb 4-4: USB disconnect, device number 2
[ 469.851354] sd 8:0:0:0: [sdg] Synchronizing SCSI cache
[ 469.851511] sd 8:0:0:0: [sdg]
[ 469.851514] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 469.852256] usb 4-4: Set SEL for device-initiated U1 failed.
[ 469.852259] usb 4-4: Set SEL for device-initiated U2 failed.

[Joschibrauchle (joschibrauchle)]

Is there any update on this problem?
It keeps happening randomly for me, and makes working with the USB device somewhat cumbersome.

[Simos Xenitellis  (simosx)]

Apparently this is a regression in the xhci code (USB3). If you connect the device to a USB2 port (if you have one) or disable xHCI in the BIOS, the problem is gone. Of course you get USB2 speeds as well.

Relevant bug reports:

"Bug#741989: linux: 3.13.5: known regression: "xHCI xhci_drop_endpoint called with disabled ep""
https://lists.debian.org/debian-kernel/2014/03/msg00153.html

"Bug 864866 - USB3 device randomly disconnecting while in use or not"
https://bugzilla.novell.com/show_bug.cgi?id=864866

"USB 3.0 corrupts NTFS disks"
https://forums.gentoo.org/viewtopic-t-963046-start-0.html

In a nutshell,
1. when something goes bad, the first dmesg messages say

[ 3888.906845] usb 4-4: reset SuperSpeed USB device number 3 using xhci_hcd
[ 3888.923000] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801de04f680
[ 3888.923002] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801de04f6c0
(probably multiple times if keep using the drive)

2. Then, the drive is disconnected and reconnected again. If you have the default setting to automount, you get many Nautilus windows opening up.

[ 4676.122427] usb 4-4: USB disconnect, device number 3
[ 4676.490858] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
[ 4676.490878] sd 6:0:0:0: [sdb]
[ 4676.490879] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 4676.490934] usb 4-4: Set SEL for device-initiated U1 failed.
[ 4676.490935] usb 4-4: Set SEL for device-initiated U2 failed.

See http://blogs.msdn.com/b/usbcoreblog/archive/2012/07/13/common-issues-in-usb-3-0-devices.aspx for more about "Set SEL".

3. After some more use, the device gives buffer I/O errors,

[ 5398.216920] Buffer I/O error on device sdb1, logical block 91570828
[ 5398.216933] Buffer I/O error on device sdb1, logical block 91570828
[ 5398.244440] Buffer I/O error on device sdb1, logical block 91570828

[Oneukum (oneukum)]

Can you test with the module parameter "autosuspend=-1" for the module "usbcore"?

[Oneukum (oneukum)]

Ping?

[Joschibrauchle (joschibrauchle)]

(In reply to Oliver Neukum from comment #14)
> Ping?

Just moved to 13.2. Will test there and report back.