On Thu, 2 Dec 2004, Andreas Theofilu wrote:

> On Wed, 1 Dec 2004 14:50:48 -0500 (EST)
> Alan Stern <[EMAIL PROTECTED]> wrote:
> 
> > 
> > It would be interesting to see the debugging information.  You should turn
> > on the USB verbose debugging and usb-storage verbose debugging options in
> > the kernel configuration, and post the system log (from dmesg, for
> > example) showing what happens when you plug in the device.
> > 
> Following is what I get with activated debugging:

> Dec  2 19:03:54 theofilu kernel:  sdb:<7>usb-storage: queuecommand called
> Dec  2 19:03:54 theofilu kernel: usb-storage: *** thread awakened.
> Dec  2 19:03:54 theofilu kernel: usb-storage: Command READ_10 (10 bytes)
> Dec  2 19:03:54 theofilu kernel: usb-storage:  28 00 00 00 00 00 00 00 08 00
> Dec  2 19:03:54 theofilu kernel: usb-storage: Bulk Command S 0x43425355 T 
> 0x61 L 4096 F 128 Trg 0 LUN 0 CL 10
> Dec  2 19:03:54 theofilu kernel: usb-storage: usb_stor_bulk_transfer_buf: 
> xfer 31 bytes
> Dec  2 19:03:54 theofilu kernel: usb-storage: Status code 0; transferred 31/31
> Dec  2 19:03:54 theofilu kernel: usb-storage: -- transfer complete
> Dec  2 19:03:54 theofilu kernel: usb-storage: Bulk command transfer result=0
> Dec  2 19:03:54 theofilu kernel: usb-storage: usb_stor_bulk_transfer_sglist: 
> xfer 4096 bytes, 1 entries
> Dec  2 19:03:55 theofilu udev: creating device node '/udev/sdb'
> 
> Dec  2 19:04:04 theofilu scsi.agent[6525]: Attribute 
> /sys/devices/pci0000:00/0000:00:10.3/usb1/1-1/1-1:1.0/host2/2:0:0:0/type does 
> not exist
> 
> Dec  2 19:04:24 theofilu kernel: usb-storage: command_abort called
> Dec  2 19:04:24 theofilu kernel: usb-storage: usb_stor_stop_transport called
> Dec  2 19:04:24 theofilu kernel: usb-storage: -- cancelling sg request
> Dec  2 19:04:24 theofilu kernel: usb-storage: Status code -104; transferred 
> 0/4096
> Dec  2 19:04:24 theofilu kernel: usb-storage: -- transfer cancelled
> Dec  2 19:04:24 theofilu kernel: usb-storage: Bulk data transfer result 0x4
> Dec  2 19:04:24 theofilu kernel: usb-storage: -- command was aborted
> Dec  2 19:04:24 theofilu kernel: usb-storage: usb_stor_Bulk_reset called
> Dec  2 19:04:24 theofilu kernel: usb-storage: usb_stor_control_msg: rq=ff 
> rqtype=21 value=0000 index=00 len=0
> 
> Dec  2 19:04:44 theofilu kernel: usb-storage: Timeout -- cancelling URB
> Dec  2 19:04:44 theofilu kernel: usb-storage: Soft reset failed: -104
> Dec  2 19:04:44 theofilu kernel: usb-storage: scsi command aborted
> Dec  2 19:04:44 theofilu kernel: usb-storage: *** thread sleeping.
> Dec  2 19:04:44 theofilu kernel: usb-storage: queuecommand called
> Dec  2 19:04:44 theofilu kernel: usb-storage: *** thread awakened.

> This looks to me like the USB-controller (not the driver) has crashed
> and doesn't answer any more. However, any help to solve this problem
> is apreciated. Thanks in advance.

I suspect it's the old Genesys problem.  There's a time delay built into 
the usb-storage driver that's supposed to compensate, but apparently for 
some drives the delay isn't long enough.

You can try editing the driver yourself to increase the delay.  In the 
kernel source, locate the file drivers/usb/storage/transport.c and edit 
it.  Inside the usb_stor_Bulk_transport subroutine there's a statement

                udelay(100);

(It's the only place "udelay" occurs in that file.)  Try increasing the 
100, say to 200, then rebuild the driver and see if it works any better.

If 200 works okay, try reducing the number to 150, or 120, or 110...  Find 
a reasonably small value that works reliably on your system.  Let me know 
what happens.

Alan Stern



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to