Alan Stern schrieb:
On Mon, 8 Jun 2009, Stefan Sassenberg wrote:
Hello,
when I plug in my usb stick the device nodes /dev/sdc and /dev/sdc1 are
created (with that line in my modprobe.conf: options usb-storage
delay_use=30).
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=14cd ProdID=8123 Rev= 2.01
S: Manufacturer=SDMMC MA8123
S: Product=USB MassStorage Device
S: SerialNumber=812320080329
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
When I try to mount /dev/sdc1 or execute fdisk /dev/sdc, it fails and
"tail -f /var/log/messages | grep usb-storage" says (at the end)
Jun 8 00:09:20 ds9 usb-storage: Attempting to get CSW...
Jun 8 00:09:20 ds9 usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
Jun 8 00:09:20 ds9 usb-storage: Status code 0; transferred 13/13
Jun 8 00:09:20 ds9 usb-storage: -- transfer complete
Jun 8 00:09:20 ds9 usb-storage: Bulk status result = 0
Jun 8 00:09:20 ds9 usb-storage: Bulk Status S 0x53425355 T 0xc2 R 0
Stat 0x0
Jun 8 00:09:20 ds9 usb-storage: -- Result from auto-sense is 0
Jun 8 00:09:20 ds9 usb-storage: -- code: 0x70, key: 0x2, ASC: 0x3a,
ASCQ: 0x0
Jun 8 00:09:20 ds9 usb-storage: Not Ready: Medium not present
Jun 8 00:09:20 ds9 usb-storage: scsi cmd done, result=0x2
Jun 8 00:09:20 ds9 usb-storage: *** thread sleeping.
ds9 ~ # uname -a
Linux ds9 2.6.29-gentoo-r4 #5 SMP Sun Jun 7 22:49:41 CEST 2009 x86_64
AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux
It also fails on my notebook:
shuttle ~ # uname -a
Linux shuttle 2.6.28-gentoo-r5 #5 SMP Sun Jun 7 22:10:08 CEST 2009 i686
Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz GenuineIntel GNU/Linux
It works in a virtual machine with an old kernel 2.6.24-gentoo-r?
The device is not physically a card reader with a removable medium, it's
an 8GB stick. What's wrong with it?
In short, what's wrong is the device is buggy. However you probably
already know that...
There's no way to tell exactly what's wrong from the information you
provided. We need to see more. Can you provide a usbmon trace
starting from the time you plug the device in and ending with the
failed mount?
And can you provide a similar trace showing it working with 2.6.24?
I put the bad trace to <http://coolmule.de/bad.tar.gz>. When creating
the good trace on the 2.6.24 vm the fdisk also failed. I repeated the
fdisk command and noticed, that it sometimes works, sometimes not. I
made a 'watch "fdisk -l /dev/sdc"' for 40 seconds on the 2.6.29 machine
and had a success rate of 7 out of 20 with no special pattern. The same
watch on the 2.6.24 (sda) had 3 failures and then 17 good runs in a row.
If you'd like to see the trace of the 2.6.24 connect,
<http://coolmule.de/good.tar.gz>, but it's a lot shorter.
--
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
