On Thu, 2003-11-13 at 21:34, Alan Stern wrote: > On Thu, 13 Nov 2003, Alex Bennee wrote: > > 1. Could this a transport problem? I'm using a hacked up version of the > > ISP116x driver which seems to work in all other respects. Do the > > WRITE_CMD's and READ_CMD's use the same low level USB transport? > > It might be a kind of transport problem. Some devices don't like it when > commands arrive too quickly. WRITEs and READs do use the same low-level > transport.
Is there some way to pace/slow down the commands at the usb level or should I tweak my transport driver to do that? > It's probably not a protocol problem. Although there used to be an > unusual_devs.h entry for the 0c76/0005 device, it's not needed in any of > the more recent kernels because of changes to the scsi layer. That explains that then, thanks. > > 3. Does anything sptring out of the attached log? I can see the -110 > > failures on the commands but basically I understand none of the details. > > If someone could at least point to a protocol vs transport problem I'd > > be flying a little less blind :-) > > Most likely it's a firmware problem. > > > usb-storage: Bulk command transfer result=-110 > > usb-storage: -- transport indicates error, resetting > > usb-storage: Bulk reset requested > > usb-storage: Bulk soft reset failed -110 > > usb-storage: scsi cmd done, result=0x70000 > > usb-storage: *** thread sleeping. > > SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 > > I/O error: dev 08:01, sector 2000 > > Nothing springs out of this immediately. The -110 (-ETIMEDOUT) error > means that the device didn't reply when it was supposed -- from your log > it looks like the firmware crashed. When you say firmware I assume you mean on the USB device itself? It makes sense, after an attempt to write sectors the device goes dead and cannot be read again without unmounting, unplugging and starting again. However according to the linux-usb compatibility chart most people don't have a problem with this device so I'm wondering where the subtle difference is? > What happens if you try using Linux 2.6.0? Its USB stack is more robust > than the one in 2.4. Unfortunately not an option. I'm getting this working for a production embedded system for which 2.6 is just too new to be an option yet. Once we start shipping version 1 I fully intend to have a go at trying out 2.6.0, it just doesn't currently line up with our release schedules :-) -- Alex, homepage: http://www.bennee.com/~alex/ A citizen of America will cross the ocean to fight for democracy, but won't cross the street to vote in a national election. -- Bill Vaughan ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
