On Thu, 15 Jul 2004, Gonzalo Payo Navarro wrote:

> Hi people, I have a problem with my pendrive "Easy Comm USB Dual Drive
> SD". This device comes with 64mb of internal memory plus it can read SD
> cards.
> 
> Its information (from /proc/bus/usb/devices)
> T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=10cc ProdID=1105 Rev= 1.00
> S:  Manufacturer=        
> S:  Product=USB Drive       
> S:  SerialNumber=4845030008EA
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50
> Driver=usb-storage
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=83(I) Atr=03(Int.) MxPS=   2 Ivl=1ms
> 
> I can mount this device and copy files with any size into it. But if I try to 
> copy big files (say 40mb) from it to my hard disk, the device start to copy, 
> but suddenly stops. The led stop blinking.
> 
> The I have to restart the computer to use it again.
> 
> Kernel: 2.6.7 bk20
> Mother board: Asus A7V600-X (with VIA Chipset) (glup!)
> EHCI Build in the kernel
> UHCI Build as a module
> MultiLUNS activated
> 
> I hope you can help me... Thanks!


The first sign of a problem is the line in your log that says:

usb-storage: Status code -84; transferred 47232/53248

That code indicates a CRC mismatch; it could arise from electrical noise 
in the USB cable or a problem with the drive.  That in itself wouldn't be 
a problem (although it's not supposed to happen so often).

But next the usb-storage issued a device reset to clear the error
condition, and the reset failed completely -- it timed out.  Maybe in such
situations we should try to do a port reset instead; that's what Windows
would do and many devices seem to support it better.

Anyway, after the failed reset the READ command was retried, and now the 
mixed-up device sent a "babble" response.  Since you've got a VIA 
controller, that was the end.  The controller shuts itself down when it 
gets babble, and from then on nothing at all can work.  I'm not sure what 
happened after that; there's a jump in your log and it looks like some 
data is missing.

I suppose for now you could use a different USB cable or move the computer
and drive away from sources of electromagnetic interference.  At some
point maybe we'll try changing the error recovery procedure in
usb-storage; if port resets do the trick then such errors could occur from
time to time and they would slow down your data transfers but ultimately
nothing would be lost.  Until then, I can't think of anything else for you
to try.

Alan Stern




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to