Johannes Erdfelt <[EMAIL PROTECTED]> writes: > On Sat, Jan 05, 2002, Peter Osterlund <[EMAIL PROTECTED]> wrote: > > > > Maybe this is such an unusual situation so that it triggered a > > firmware bug in the drive, causing it to misbehave badly on the bus. > > It definately did get to the disconnect phase, which means it got > through the parsing stage and there was a race condition. > > This sounds like it had a corrupted descriptor table. Did you get any > odd messages when the device connected?
Not that I remember. Unfortunately, I deleted the log file, because it got corrupted after the panic. However, there had been several successful commands to the drive before the first WRITE command, so I guess the descriptor table can not have been too corrupted. That's why I guessed the drive did a disconnect/reconnect/disconnect just before the panic. It's possible that when reconnecting, the descriptor table was corrupt. -- Peter Osterlund - [EMAIL PROTECTED] http://w1.894.telia.com/~u89404340 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
