On Wed, 24 May 2006, Norbert Preining wrote: > On Mit, 24 Mai 2006, Alan Stern wrote: > > Or maybe the disk's firmware crashes and stops responding, but the driver > > waits for the current command to time out before doing a reset. I guess > > there's no easy way to tell the difference between a long blockage and a > > crash. Increase the timeout limit perhaps, and see if the resets go away. > > (The default timeout is defined as SD_TIMEOUT in drivers/scsi/sd.c and it > > is set to 30 seconds.) > > I have set it to 60 * Hz and retried, but with the same effect, again 29 > resets (strange that it is always 29, mysteries I like sooo much ;-)
Setting it down to 10 * Hz would improve your throughput -- less time lost waiting for timeouts. :-) It might not be a bad idea to follow Pete's advice and use usbmon. Instructions are in Documentation/usb/usbmon.txt. You'll get a lot of output, not very easy to interpret. But it shouldn't be hard to find the sections where the 29 timeouts and resets occur, just by searching for large jumps in the timestamps. If you post the region surrounding one of those occurrences, I can tell you what's going on. Alan Stern ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
