On Fri, 15 Jul 2005 10:15:57 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> > d83010e8 697581267 S Bi:005:02 -115 13 < > > What's this? Trying to read another CSW? No wonder you hung... Correct, it was a bug. > > Look at the jump in the timestamp. It's where I became tired from waiting > > and pulled the cable. The unlink itself is not captured by usbmon, because > > they are rather reliable normally, and you see a callback with status -104. > > I skipped on implementing that. But I guarantee you that ub tries an unlink > > from a timer. > > Are you sure it did so in this case? The presence of those two extra CSW > reads indicates that _something_ in ub wasn't working right. No doubt about that, but I'm sure the unlink was there. I probably should have not brought it up, because it's not reproduceable. -- Pete ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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
