On Wed, 14 Jan 2004, jjluza wrote: > > I just looked back at your original problem report, and I saw this in your > > log file: > > > > Jan 9 06:34:05 client kernel: usb-storage: Command WRITE_10 (10 bytes) > > Jan 9 06:34:05 client kernel: usb-storage: 2a 00 00 4f 09 57 00 00 80 00 > > Jan 9 06:34:05 client kernel: usb-storage: Bulk Command S 0x43425355 T 0x14ea L > > 65536 F 0 Trg 0 LUN 0 CL 10 > > Jan 9 06:34:05 client kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 > > bytes > > Jan 9 06:34:05 client kernel: usb-storage: Status code 0; transferred 31/31 > > Jan 9 06:34:05 client kernel: usb-storage: -- transfer complete > > Jan 9 06:34:05 client kernel: usb-storage: Bulk command transfer result=0 > > Jan 9 06:34:05 client kernel: usb-storage: usb_stor_bulk_transfer_sglist: xfer > > 65536 bytes, 16 entries > > Jan 9 06:34:30 client kernel: usb 1-3: control timeout on ep0in > > Jan 9 06:34:35 client kernel: usb 1-3: control timeout on ep0in > > > > What on earth are these messages doing here? 1-3 is the usb-storage > > device in question. There shouldn't be any control transfers going on at > > this point, only the bulk-out transfer. This looks very strange... > > > > > I don't understand these messages so I can't answer you ;) > I enable verbose scsi, verbose usb and verbose usb-storage > I load modules sd_mod and usb-storage, and ehci is compiled in.
The questions were really meant for other readers on the USB development list; I didn't expect you to have the answers. > > Do you see this same sort of thing in the log with max_sectors set to 16? > > > Yes > > > > Just for kicks, see what happens when you set max_sectors to 2. (!) > > > You can find it here : > http://jjluza.free.fr/log_new(with_max_sectors_is_2).txt > It seems that the messages are nearly the same. Yes. And in fact, the block layer won't let max_sectors get any smaller than 8. But changing it doesn't seem to have improved anything. > > Also, I can't remember if you've already posted this information. Could > > you send the output from lsusb, or else the contents of > > /proc/bus/usb/devices, with your drive plugged in? > > > Yes, I have already posted it. You can find all file I posted here : > http://jjluza.free.fr/ > You can find contents of /proc/bus/usb/devices here : > http://jjluza.free.fr/infos_usbstorage.txt > with other informations about the bad device > > I hope these information can help you to find a solution ;) I looked, but I don't see any clear answer. These Genesys Logic devices have weird problems that nobody really seems to understand. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
