On Thu, 13 Nov 2003, Alex Bennee wrote: > Hi, > > I'm currently trying to get my Freecom 64MB stick to work with my > embedded board. The device id reports as: > > idVendor 0x0c76 > idProduct 0x0005 > > Which doesn't actually match the Freecom devices listed on > linux-usb.org's compatibility list (but matches a number of other flash > storage devices). > > I can mount the disk and read files already there but if I try and store > files it fails (sometime corrupting the filesystem). It seems that at > least some of the WRITE_CMD's are failing (see attached log). If I could > ask a few questions of the more knowledgeable usb hackers: > > 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. > 2. Could this be a protocol problem? I googled for the device ID and saw > several patches floating about from last year that added unusual_devs > entries. The changes for this device don't seem to exist in the latest > tree's (I'm currently on 2.4.22). Where they bogus changes or did they > conflict with other devices? 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. > 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. What happens if you try using Linux 2.6.0? Its USB stack is more robust than the one in 2.4. Alan Stern ------------------------------------------------------- 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
