On Tue, Feb 22, 2005 at 10:27:51AM -0500, Alan Stern wrote: > If I'm reading your timestamps correctly (seconds and fractions of a > second), you made the stack dump only 4 seconds after things stopped > happening. That's not long enough; the SCSI drivers have a timeout of 10 > seconds (I think) for reads and 30 seconds for error recovery, which > proceeds in several stages with lots of retries. You should wait a few > minutes for things to settle down before assuming that the system has > hung.
The system isn't hung. (cat is hung, until the timeout completes.) usb- storage/ub is timing out as a result of serial being read. All I want is to be able to read the serial (and product and manufacturer strings) without risking interference with other communications with the device. (I've designed my code around the fact that the timeout periods are very long: writing data, and all other access, is done in a thread; if writing data takes more than ten seconds, the main thread gives up and moves on, assuming that the writing thread will wake back up once either the timeout completes or the player pulls his pen drive out, and assuming that anything else is a kernel bug. So far, that's held--2.6 is a big improvement in this regard.) -- Glenn Maynard ------------------------------------------------------- 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
