Re: Unable to access USB mass storage device with xhci. okay with ehci

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote:

> 
> Is that really all?  Was there a "UAS is blacklisted for this device"  
> line in the kernel log?  It looks like the usb-storage driver didn't do
> anything at all with the device.

Yes that's it. Using xhci at super speed, blacklisting uas is ignored
and the uas module apparently loaded anyway. 

Here's a small snipet of dmesg w/uas blacklisted in
usr/lib/modprobe.d/dist-blacklist.conf using xhci at super speed.




3.329222] usb 1-10: new full-speed USB device number 10 using xhci_hcd
[    3.494369] usb 1-10: New USB device found, idVendor=0cf3,
idProduct=0036
[    3.494372] usb 1-10: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[    3.500030] usbcore: registered new interface driver usb-storage
[    3.501375] usbcore: registered new interface driver uas
[    3.502435] ums-realtek 1-9:1.0: USB Mass Storage device detected
[    3.512254] scsi host5: usb-storage 1-9:1.0


But with ehci or xhci w/usb2 cable blacklisting succeeded and a message
was printed in the logs. Also note the Quirk match.


[  192.802720] xhci_hcd 0000:00:14.0: Endpoint 0x2 ep reset callback
called
[  192.844585] usb 1-2: UAS is blacklisted for this device, using
usb-storage instead
[  192.844588] usb-storage 1-2:1.0: USB Mass Storage device detected
[  192.844990] usb-storage 1-2:1.0: Quirks match for vid 174c pid 55aa:
400000
[  192.845004] scsi host5: usb-storage 1-2:1.0
[  192.845065] usbcore: registered new interface driver usb-storage




Another usbmon trace but with the uas module renamed.

ffff88040c22f6c0 1404716006 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <
ffff88040c22f6c0 1404716087 C Ci:2:001:0 0 4 = a0020000
ffff88040c22f6c0 1404716097 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff88040c22f6c0 1404716114 C Ci:2:001:0 0 4 = 03020100
ffff88040c22f6c0 1404716120 S Co:2:001:0 s 23 01 0010 0002 0000 0
ffff88040c22f6c0 1404716132 C Co:2:001:0 0 0
ffff88040d21fd80 1404817133 S Ii:2:001:1 -115:2048 4 <
ffff88040c22f6c0 1404817151 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff88040c22f6c0 1404817183 C Ci:2:001:0 0 4 = 03020000
ffff88040c22f6c0 1404817325 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff88040c22f6c0 1404817342 C Ci:2:001:0 0 4 = 03020000
ffff88040c22f6c0 1404817347 S Co:2:001:0 s 23 03 0004 0002 0000 0
ffff88040c22f6c0 1404817360 C Co:2:001:0 0 0
ffff88040c22f6c0 1404868129 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff88040c22f6c0 1404868161 C Ci:2:001:0 0 4 = 03021000
ffff88040c22f6c0 1404919143 S Co:2:001:0 s 23 01 0014 0002 0000 0
ffff88040c22f6c0 1404919184 C Co:2:001:0 0 0
ffff88040c22f6c0 1404919192 S Co:2:001:0 s 23 01 001d 0002 0000 0
ffff88040c22f6c0 1404919205 C Co:2:001:0 0 0
ffff88040c22f6c0 1404919209 S Co:2:001:0 s 23 01 0019 0002 0000 0
ffff88040c22f6c0 1404919220 C Co:2:001:0 0 0
ffff88040c22f6c0 1404919224 S Co:2:001:0 s 23 01 0010 0002 0000 0
ffff88040c22f6c0 1404919235 C Co:2:001:0 0 0
ffff88040c22f6c0 1404919240 S Ci:2:001:0 s a3 00 0000 0002 0004 4 <
ffff88040c22f6c0 1404919256 C Ci:2:001:0 0 4 = 03020000
ffff88040c22f6c0 1404930049 S Ci:2:002:0 s 80 06 0100 0000 0008 8 <
ffff88040c22f6c0 1404930103 C Ci:2:002:0 0 8 = 12010003 00000009
ffff88040c22f6c0 1404930130 S Ci:2:002:0 s 80 06 0100 0000 0012 18 <
ffff88040c22f6c0 1404930179 C Ci:2:002:0 0 18 = 12010003 00000009
4c17aa55 00010203 0101
ffff88040c22f6c0 1404930195 S Ci:2:002:0 s 80 06 0f00 0000 0005 5 <
ffff88040c22f6c0 1404930235 C Ci:2:002:0 0 5 = 050f1600 02
ffff88040c22f6c0 1404930250 S Ci:2:002:0 s 80 06 0f00 0000 0016 22 <
ffff88040c22f6c0 1404930288 C Ci:2:002:0 0 22 = 050f1600 02071002
02000000 0a100300 0e00010a ff07
ffff88040c22f6c0 1404930306 S Ci:2:002:0 s 80 06 0200 0000 0009 9 <
ffff88040c22f6c0 1404930402 C Ci:2:002:0 0 9 = 09027900 010100c0 12
ffff88040c22f6c0 1404930420 S Ci:2:002:0 s 80 06 0200 0000 0079 121 <
ffff88040c22f6c0 1404930511 C Ci:2:002:0 0 121 = 09027900 010100c0
12090400 00020806 50000705 81020004 0006300f 00000007
ffff88040c22f480 1404930533 S Ci:2:002:0 s 80 06 0300 0000 00ff 255 <
ffff88040c22f480 1404930575 C Ci:2:002:0 0 4 = 04030904
ffff88040c22f480 1404930597 S Ci:2:002:0 s 80 06 0303 0409 00ff 255 <
ffff88040c22f480 1404930644 C Ci:2:002:0 0 32 = 20035500 53004200
33002d00 53004100 54004100 2d005500 41005300 50003100
ffff88040c22f480 1404930657 S Ci:2:002:0 s 80 06 0302 0409 00ff 255 <
ffff88040c22f480 1404930696 C Ci:2:002:0 0 18 = 12035000 6c007500
67006100 62006c00 6500
ffff88040c22f480 1404930707 S Ci:2:002:0 s 80 06 0301 0409 00ff 255 <
ffff88040c22f480 1404930748 C Ci:2:002:0 0 26 = 1a033100 32003300
34003500 36003700 38003900 30003100 3400
ffff88040c22f900 1404932378 S Co:2:002:0 s 00 09 0001 0000 0000 0
ffff88040c22f900 1404932421 C Co:2:002:0 0 0





> 
> This seems to be a separate problem from the original one.
> 
> > usbmon trace using ehci:
> ...
> 
> Comparing this with the original usbmon trace, it looks like the first
> problem in the xHCI trace shows up when we try to transfer more than
> 122880 bytes.  A 196608-byte transfer has to be aborted after 30 
> seconds, and only 65536 bytes were received.  (Note that 122880-byte 
> transfers succeeded in both the EHCI and xHCI-with-a-USB-2-cable 
> traces.)
> 
> Perhaps this drive needs some sort of max_sectors restriction.
> 
> Alan Stern

Okay, is there a patch i can try?

Thanks for your help with this.

Steve




--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux