linux-kernel - Re: usb 3.0 hard drive doesn't work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 07 Oct 2012 23:31:49 +0200
From:	Daniel Mack <zonque@...il.com>
To:	王思源 <wangsiyuanbuaa@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-usb <linux-usb@...r.kernel.org>
Subject: Re: usb 3.0 hard drive doesn't work

(cc linux-usb)

On 07.10.2012 10:48, 王思源 wrote:
> hi,
> i have a usb 3.0 hard drive and a laptop with usb 3.0 port.
> when the hard drive is connected to the usb 3.0 port, the drive could
> not be found.
> the dmesg output is listed below.
> additinal info:
> 1) the usb 3.0 hard drive can be found when connected to usb 2.0 port.
> 2) the usb 2.0 hard drive can be found when connected to usb 3.0 port.
> 3) mouse works when connected to the usb 3.0 port.
> 4) it is archlinux and kernel version is 3.5.5-1-ARCH
> it seems that it is not the linux driver's problem, because the mouse
> could work and the hard drive is found due to the dmesg.
> is this a bug?
> would someone help me?
> thank you!
> 
> dmesg out put when usb 3.0 hard drive is conneted to usb 3.0 port:
> [  646.077385] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
> [  646.171319] usbcore: registered new interface driver uas
> [  646.175313] Initializing USB Mass Storage driver...
> [  646.175501] scsi4 : usb-storage 2-2:1.0
> [  646.175665] usbcore: registered new interface driver usb-storage
> [  646.175667] USB Mass Storage support registered.
> [  657.149403] scsi 4:0:0:0: Direct-Access     WD       My Passport
> 0730 1016 PQ: 0 ANSI: 6
> [  657.149974] sd 4:0:0:0: [sdb] 976707584 512-byte logical blocks:
> (500 GB/465 GiB)
> [  657.150223] sd 4:0:0:0: [sdb] Write Protect is off
> [  657.150232] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
> [  657.150456] sd 4:0:0:0: [sdb] No Caching mode page present
> [  657.150462] sd 4:0:0:0: [sdb] Assuming drive cache: write through
> [  657.151436] sd 4:0:0:0: [sdb] No Caching mode page present
> [  657.151440] sd 4:0:0:0: [sdb] Assuming drive cache: write through
> [  657.159907]  sdb: sdb1
> [  657.160852] sd 4:0:0:0: [sdb] No Caching mode page present
> [  657.160858] sd 4:0:0:0: [sdb] Assuming drive cache: write through
> [  657.160861] sd 4:0:0:0: [sdb] Attached SCSI disk
> [  657.268875] usb 2-2: Device not responding to set address.
> [  657.471456] usb 2-2: Device not responding to set address.
> [  657.674211] usb 2-2: device not accepting address 2, error -71
> [  657.780745] usb 2-2: Device not responding to set address.
> [  657.983519] usb 2-2: Device not responding to set address.
> [  658.186214] usb 2-2: device not accepting address 2, error -71
> [  658.292717] usb 2-2: Device not responding to set address.
> [  658.495537] usb 2-2: Device not responding to set address.

>From the logs, this smells like a power supply problem. Can you connect
an external supply or do you have a powered USB3 hub? It's possible that
it draws less power in USB2.0 mode, so that would explain what you describe.

But I could be wrong alltogether :)


Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/