On Wed, 1 Mar 2006, Marc Singer wrote: > I have this: > > e2372840 1612603151 C Ci:009:00 -121 32 = 09022000 0103fac0 01090400 0002ff00 > 00fa0705 02024000 00070581 02400000 > e2372840 1612603151 S Ci:009:00 s 80 06 0200 0000 0400 1024 < > > which says to me that the callback was received before the submission.
Yes and no. There was a callback received before a submission, but the callback was for a _prior_ submission, not this one. > There is not another e2372840 URB after this point in the capture > which runs for 1000's of lines. So that URB submission never completed. > Other places in the protocol trace show that the S preceeds the C, > especially where there is a significant amount of time between the > two. > > So, how can this happen? Am I seeing an error in USBMON? No, you are misinterpreting the output. For any particular submission, the S line _always_ precedes the C line. You can get confused by the fact that a driver frequently will resubmit the very same URB as soon as the URB completes, so it looks like the C immediately precedes the S. That's misleading; the C really matches a much earlier S and the S really matches a much later C. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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
