El 05/08/13 11:18, Alan Stern escribió:
On Mon, 5 Aug 2013, [ISO-8859-1] Alex Villac�s Lasso wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=60685
Posting in the mailing list as requested by Greg Kroah-Hartman <mailto:greg@xxxxxxxxx>
Problem description:
All the USB memory sticks I have work correctly under 3.11-rc1, except one. This
memory stick is the same Corsair Voyager that was involved inbug #11260 <https://bugzilla.kernel.org/show_bug.cgi?id=11260>. On
3.10 the stick works correctly. On 3.11, after insertion, the same stick fails
to proceed to the point where partitions are reported, and dmesg shows this:
[ 1972.319036] usb 1-5: new high-speed USB device number 7 using ehci-pci
[ 1972.436100] usb 1-5: New USB device found, idVendor=090c, idProduct=1000
[ 1972.436109] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1972.436114] usb 1-5: Product: Flash Voyager
[ 1972.436119] usb 1-5: Manufacturer: Corsair
[ 1972.436123] usb 1-5: SerialNumber: A100000000000604
[ 1972.437522] usb-storage 1-5:1.0: USB Mass Storage device detected
[ 1972.439932] scsi9 : usb-storage 1-5:1.0
[ 1973.443479] scsi 9:0:0:0: Direct-Access Corsair Flash Voyager 1100 PQ: 0 ANSI: 0 CCS
[ 1973.444148] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 1973.446828] sd 9:0:0:0: [sdc] 990208 512-byte logical blocks: (506 MB/483 MiB)
[ 1973.447837] sd 9:0:0:0: [sdc] Write Protect is off
[ 1973.447842] sd 9:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 1973.448838] sd 9:0:0:0: [sdc] No Caching mode page present
[ 1973.448845] sd 9:0:0:0: [sdc] Assuming drive cache: write through
(...)
[ 2003.814036] usb 1-5: reset high-speed USB device number 7 using ehci-pci
(...)
[ 2018.916037] usb 1-5: device descriptor read/64, error -110
I am currently bisecting this to discover what is going on.
Have you tried this patch?
http://marc.info/?l=linux-usb&m=137523956310060&w=2
Alan Stern
I have just tested the patch, and it fixes the bug in 3.11-rc4.
--
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
