On Sat, 19 Feb 2005, Samuel Colin wrote: > > I mean the disk or its USB interface is misbehaving, even though the > > kernel and drivers all seem to be acting correctly. > > > Maybe a fuzzy point in the USB2 or scsi specifications everyone interpreted > differently.
I doubt it. Certainly not in the SCSI spec; the command that failed was a simple READ just like a whole lot of others that succeeded. And didn't you say that everything worked with the uhci-hcd driver? That wouldn't change what SCSI commands were used. > > I wonder if increasing it more, say to 200, would have an effect? > > Perhaps I'm fixated on that delay, but it's the only factor I've ever seen > > that was related to the kind of problem you have. > > > No, I just tried (removed the experimental patch and increased to 200), the > fsck on the disk hung again. Then it's beyond me... Without having a clue as to what's going wrong, the best we can do is to clean up after a failure, like that new patch does. 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
