USB3 Western Digital external HDD no longer detected after upgrade to 3.5.4 kernel

Jaysonfw · 10-12-2012, 11:42 AM

Hi All,
I'm having a difficult time troubleshooting my USB3 HDD problem and was hoping for some help. After upgrading my kernel from 3.2.28 to 3.5.4-generic using Pat's config-generic in testing, my USB3 external HDD is no longer detected. If I plug it into a 2.0 port it is detected. If I plug any other device in the 3.0 port, they are detected. If I boot with the 3.2.29 kernel the USB3.0 HDD is detected on the 3.0 port. Just the Western Digital device is not detected in the USB3 port when booting from 3.5.4. Is this a bug in the kernel. Any help is greatly appreciated.

Here's my dmesg. I did a bunch of google searches on warnings, but couldn't find a solution.

[ 320.939908] usb 4-1: New USB device found, idVendor=1058, idProduct=1130
[ 320.939914] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 320.939917] usb 4-1: Product: My Book 1130
[ 320.939920] usb 4-1: Manufacturer: Western Digital
[ 320.939923] usb 4-1: SerialNumber: 5743415A4132373431383832
[ 320.941051] scsi11 : usb-storage 4-1:1.0
[ 331.937713] scsi 11:0:0:0: Direct-Access WD My Book 1130 1012 PQ: 0 ANSI: 6
[ 334.402202] sd 11:0:0:0: [sdb] 3906963456 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 334.402317] sd 11:0:0:0: [sdb] Write Protect is off
[ 334.402322] sd 11:0:0:0: [sdb] Mode Sense: 47 00 10 08
[ 334.402439] sd 11:0:0:0: [sdb] No Caching mode page present
[ 334.402441] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[ 334.402959] sd 11:0:0:0: [sdb] No Caching mode page present
[ 334.402961] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[ 334.421312] sdb: sdb1
[ 334.422020] sd 11:0:0:0: [sdb] No Caching mode page present
[ 334.422023] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[ 334.422026] sd 11:0:0:0: [sdb] Attached SCSI disk
[ 334.423425] usb 4-1: Disable of device-initiated U1 failed.
[ 334.423501] usb 4-1: Disable of device-initiated U2 failed.
[ 334.525095] usb 4-1: Device not responding to set address.
[ 334.725874] usb 4-1: Device not responding to set address.
[ 334.926718] usb 4-1: device not accepting address 17, error -71
[ 335.028702] usb 4-1: Device not responding to set address.
[ 335.229593] usb 4-1: Device not responding to set address.
[ 335.430447] usb 4-1: device not accepting address 17, error -71
[ 335.532435] usb 4-1: Device not responding to set address.
[ 335.733333] usb 4-1: Device not responding to set address.
[ 335.934191] usb 4-1: device not accepting address 17, error -71
[ 336.036170] usb 4-1: Device not responding to set address.
[ 336.237066] usb 4-1: Device not responding to set address.
[ 336.437919] usb 4-1: device not accepting address 17, error -71
[ 336.437966] usb 4-1: USB disconnect, device number 17
[ 336.439306] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88009409a6c0
[ 336.439314] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88009409a680
[ 336.540919] usb 4-1: Device not responding to set address.
[ 336.741789] usb 4-1: Device not responding to set address.
[ 336.942659] usb 4-1: device not accepting address 18, error -71
[ 337.044621] usb 4-1: Device not responding to set address.
[ 337.245513] usb 4-1: Device not responding to set address.
[ 337.446390] usb 4-1: device not accepting address 19, error -71
[ 337.548369] usb 4-1: Device not responding to set address.
[ 337.749249] usb 4-1: Device not responding to set address.
[ 337.950144] usb 4-1: device not accepting address 20, error -71
[ 338.052105] usb 4-1: Device not responding to set address.
[ 338.252986] usb 4-1: Device not responding to set address.
[ 338.453880] usb 4-1: device not accepting address 21, error -71
[ 338.453893] hub 4-0:1.0: unable to enumerate USB device on port 1

Didier Spaier · 10-12-2012, 02:17 PM

The only culprit I can think of is the xhci-hcd kernel module.

On my Slackware 13.37 "modinfo xhci-hcd" returns

Code:

filename:       /lib/modules/2.6.37.6-smp/kernel/drivers/usb/host/xhci-hcd.ko
license:        GPL
author:         Sarah Sharp
description:    'eXtensible' Host Controller (xHC) Driver
alias:          pci:v*d*sv*sd*bc0Csc03i30*
depends:        
vermagic:       2.6.37.6-smp SMP mod_unload 686 
parm:           link_quirk:Don't clear the chain bit on a link TRB (int)

I would compare "modinfo xhci-hcd" on both 3.2.29 & 3.5.4 kernels and maybe try to fiddle with the module parameter(s).

You can also blacklist that module and see what happens. Normally you shouldn't have USB 3 without it though.

EDIT Or conversely you could load the module manually before plugging in the drive and see what happens. If that works, just have it loaded at start up.