> <...> > > usb-storage: Command READ_10 (10 bytes) > > usb-storage: 28 00 00 00 00 00 00 00 08 00 > > usb-storage: Bulk Command S 0x43425355 T 0x3325 L 4096 F 128 Trg 0 LUN 0 CL 10 > > usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > > usb-storage: Status code 0; transferred 31/31 > > usb-storage: -- transfer complete > > usb-storage: Bulk command transfer result=0 > > usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries > > usb 1-1: control timeout on ep0in > > usb 1-1: control timeout on ep0in > > usb 1-1: control timeout on ep0in > > usb 1-1: control timeout on ep0in > > Where did these messages come from? usb-storage doesn't produce them. > There must have been some other program trying to access the drive at the > same time as usb-storage, interfering with its operation. Probably a > hotplug program or an automounter. You might be able to learn more from > usbfs_snoop.
All tools that poke at the hardware can not run, I did a chmod a-x. If it helps, I can build a static kernel again. > How long did you let that reset go on for before getting this stack dump? > If it was less than 20 seconds then the reset simply hasn't timed out yet. I did not wait that long. Will try again tomorrow. -- USB is for mice, FireWire is for men! sUse lINUX ag, nÃRNBERG ------------------------------------------------------- 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_idP47&alloc_id808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
