At this point, it's not clear to me that there's any real error happening except in the recovery code. I'm not saying there isn't a second problem -- only that there's only evidence of that one problem (in fault recovery) just now. And having the fault recovery work right will certainly help turn up proof if there really is some other problem.
Yes, maybe the original error is just a random fault, and the
usb_bulk/control_msg timeouts are the only real problem. However, the new
changes mean that usb_control_msg() is no longer called by usb-storage. Maybe something else will malfunction instead.
We don't have testing feedback from that new 2.5 code yet. Yes, maybe it'll help us get a better handle on what's going on in the earlier stages.
On the other hand, I'd certainly expect that the fault recovery code would work ... so fixing that oops should get past the problem Andras reported. We don't know that there'd be a "next problem".
> Also, Mitch's comments
indicate to me that this is likely to be something more than a random fault.
Not that we know where it'd be!
Maybe. By the way, do you know whether that device-state-after-reset fix I sent in last week is also needed in 2.4.21?
Shouldn't be. The 2.4 code doesn't track the chapter 9 state transitions at all, it just trusts everyone Do Right (not a good thing to trust).
- Dave
------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
