On Thu, 01 Mar 2007 08:40:15 +0200, Antti P Miettinen <[EMAIL PROTECTED]> wrote:
> etc.. and finally hard failure: > > [17181900.808000] ehci_hcd 0000:03:0c.2: XactErr, ep3in, token=0038c948 > [17181900.808000] ehci_hcd 0000:03:0c.2: XactErr, ep0out, token=80008148 > [17181900.808000] ehci_hcd 0000:03:0c.2: devpath 1 ep0out 3strikes,t=80008148 OK, not comment on this, maybe David would... > In the usbmon log as far as I've understood we first get one EPIPE > which corresponds to the token having transfer length 0x38 above and > then start getting EPROTO: > > f76228c0 30344747 C Bi:002:02 -32 39424 = 36629c1a dc40077f eefbb3df d85cf2d0 > 09661035 40829685 d6fa47bf d1ff4134 -32 is a STALL condition. I wish you found the S(ubmit) for this C(allback). The length returned in C events is the actual length, transferred before the stall happened. Although likely it was 39480, like in consequent requests. Everything beyond the stall, I can't comment. The -71 happens if the device fails to respond at the lowest level (ignores tokens). In storage world, we must clear stalls. In your trace there was no attempt to clear anything, just next transfer resubmitted. But perhaps it's all right for your class and/or protocol. > Does anyone have tools/scripts for decoding the usbmon logs? You don't really need them all that much, as long as you do not try to decode the data. Just look at the usbmon.txt, and follow from there word by word, left to right. -- Pete ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
