On Thu, 1 Apr 2004, Brad Campbell wrote:
Indeed. One thing I did find interesting though is that windows recovered whereas linux needs an unplug/plug to recover (or sometimes a power cycle). I include the bit of USB-Snoopy log that shows the urb going down, the lockup and recovery.
If we could get linux to recover these devices then I guess 1 lockup for 10 seconds or so every 500mb is better than a complete freeze.
Regards, Brad
Windows performs a port reset. The code for doing this on Linux has always been a bit buggy, although it's getting better. However, the delay would be a lot longer than 10 seconds since Linux tries very hard to recover from errors without doing anything as drastic as a port reset. The actual delay (when the port reset stuff starts working right) will probably be more like 70 seconds, maybe longer.
After the reset Windows presumably simply repeats the WRITE command. Since the same data gets sent the second time as the first, why doesn't
the device just lockup again?
Ahah, that's the thing. It's not locking up on the actual data URB, it locks up on the URB after the data was sent. So from what I gather, the data makes it to the disk, it just can't retrieve the status of the transfer.
Brad
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
