174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled
[1.] 174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled [2.] I have a 1 TB Western Digital drive in a USB 3.0 HDD dock that will not automount 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 using LUKS. 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. [3.] [4.] Linux version 3.13.0-031300-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201401192235 SMP Mon Jan 20 03:36:48 UTC 2014 [5.] Not applicable [6.] None [7.] lsb_release -rd Description:Ubuntu 13.10 Release:13.10 [7.1] sh ver_linux Linux username 3.13.0-031300-generic #201401192235 SMP Mon Jan 20 03:36:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Gnu C 4.8 Gnu make 3.81 binutils 2.23.52.20130913 util-linux 2.20.1 mount support module-init-tools 9 e2fsprogs 1.42.8 pcmciautils018 PPP2.4.5 Linux C Library2.17 Dynamic linker (ldd) 2.17 Procps 3.3.3 Net-tools 1.60 Kbd1.15.5 Sh-utils 8.20 wireless-tools 30 Modules Loaded parport_pc ppdev rfcomm bnep bluetooth snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec nls_iso8859_1 snd_hwdep x86_pkg_temp_thermal intel_powerclamp snd_pcm snd_page_alloc coretemp snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_intel snd_seq lp snd_seq_device snd_timer mei_me kvm mei snd parport soundcore serio_raw lpc_ich microcode mac_hid hid_generic usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel nouveau aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci mxm_wmi libahci i2c_algo_bit ttm e1000e drm_kms_helper drm ptp pps_core wmi video [7.2] cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz stepping: 3 microcode : 0x9 cpu MHz : 3900.722 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid bogomips: 7000.12 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz stepping: 3 microcode : 0x9 cpu MHz : 3900.039 cache size : 8192 KB physical id : 0 siblings: 8 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
Re: 174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled
Actually, the USB3 device I'm using, a Unitek Y-1072 HDD dock, works fine with a WD 500 GB drive using XHCI, so it seems like it's something to do with the larger drive. I have also tried with a Rosewill RX35-AT-SU3 external enclosure and a Rosewill RX-DU300 HDD dock. All failed with the 1 TB drive. Transcend 16 GB flash drives work fine with XHCI, too. As noted in my problem description, I RMA'd the 1 TB drive and the replacement drive fails with the same error, though it too works with USB2 via EHCI. On 01/22/2014 02:20 AM, David Laight wrote: From: Jay S [2.] I have a 1 TB Western Digital drive in a USB 3.0 HDD dock that will not automount 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 I think that is an ETIMEDOUT error sending USB_REQ_SET_CONFIGURATION from usb_reset_configuration() in usb/core/message.c I presume this is plugged into one of the motherboard USB3 sockets (so using the intel xhci host controller)? Have you tried any other USB3 devices? There might be a more generic problem with USB3 on that motherboard. David -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled
Hi Sarah, I haven't tried using a USB 2.0 cable to attach the dock/drive, but I have disabled XHCI in my BIOS and the dock and 1 TB drive work fine at USB 2.0 speeds using EHCI. According to the manufacturer, the dock is designed for drives up to 4 TB. On 01/29/2014 06:33 PM, Sarah Sharp wrote: On Wed, Jan 22, 2014 at 08:51:31AM -0800, Jay S wrote: Actually, the USB3 device I'm using, a Unitek Y-1072 HDD dock, works fine with a WD 500 GB drive using XHCI, so it seems like it's something to do with the larger drive. I have also tried with a Rosewill RX35-AT-SU3 external enclosure and a Rosewill RX-DU300 HDD dock. All failed with the 1 TB drive. Transcend 16 GB flash drives work fine with XHCI, too. As noted in my problem description, I RMA'd the 1 TB drive and the replacement drive fails with the same error, though it too works with USB2 via EHCI. Have you tried connecting the drive with a USB 2.0 cable to the xHCI port? That would be good to rule out issues with xHCI vs EHCI. Perhaps the dock simply isn't designed to work with the bigger drive at USB 3.0 speeds? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 174c:5106 1 TB External USB 3.0 Drive Fails to Automount through USB 3.0 dock with XHCI Enabled
Thanks Sarah. I appreciate your efforts. A new BIOS (F8) was released on 1/24 for my motherboard, and I flashed it with that to see if that made a difference, but it did not. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
More Info
I tried yet another USB 3.0 external HDD enclosure with the 1 TB WD drive that has been the source of all these problems. This one is made by Icy Dock. It's a MB080U35-1SB, and has USB 3.0 as well as eSATA. I figured the eSATA would work even if the USB 3.0 failed. Eureka! It works via USB 3.0. The output of dmesg is as follows: [26464.898990] usb 4-6.4: new SuperSpeed USB device number 5 using xhci_hcd [26464.914507] usb 4-6.4: New USB device found, idVendor=174c, idProduct=55aa [26464.914516] usb 4-6.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [26464.914521] usb 4-6.4: Product: ASMT1051 [26464.914524] usb 4-6.4: Manufacturer: asmedia [26464.914528] usb 4-6.4: SerialNumber: 123456789012 [26464.916373] usb-storage 4-6.4:1.0: USB Mass Storage device detected [26464.916518] usb-storage 4-6.4:1.0: Quirks match for vid 174c pid 55aa: 40 [26464.916643] scsi9 : usb-storage 4-6.4:1.0 [26465.915592] scsi 9:0:0:0: Direct-Access ASMT 2105 0PQ: 0 ANSI: 6 [26465.916073] sd 9:0:0:0: Attached scsi generic sg2 type 0 [26465.917221] sd 9:0:0:0: [sdb] Spinning up disk... [26466.920665] ...ready [26480.998284] sd 9:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [26480.998581] sd 9:0:0:0: [sdb] Write Protect is off [26480.998587] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00 [26480.998859] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [26481.010073] sdb: unknown partition table [26481.011194] sd 9:0:0:0: [sdb] Attached SCSI disk [26531.348333] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [26531.385060] systemd-hostnamed[8286]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! This one uses a different chipset than any of the others I've tried. I hope this helps. I am even more hopeful that this wasn't a wild goose chase I led you on due to problems with these external docks/enclosures and not something in the kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
