On Mon, 2 Jun 2003, David Brownell wrote: > Alan Stern wrote: > > > 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.
Indeed. Andras or Mitch, please let us know when you've had a chance to try the new version of the USB drivers (as of Monday June 2). > 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". I have this recurring fantasy that the fault recovery will get so good no one will notice the errors any more, in spite of them having a systematic and easy-to-fix (if not easy-to-find!) cause. > > 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! Admittedly, "somewhere in the EHCI driver or the HC itself" isn't a very specific guess. Alan Stern ------------------------------------------------------- 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
