Topic: dmesg full of usb messages

Hi folks.

Great device, and a great community supporting it. I'm curious about a recurring message in my logs.

dmesg shows:

[55372.073424] pxau2h-ehci pxau2h-ehci: devpath 1.3 ep3in 3strikes
[55372.073460] usb 1-1.3: unlink qh128-0601/ff3aa580 start 127 [1/2 us]
[55372.073487] pxau2h-ehci pxau2h-ehci: reused qh ff3aa580 schedule
[55372.073505] usb 1-1.3: link qh128-0601/ff3aa580 start 127 [1/2 us]

I'm using a wired eithernet link hanging off the USB port.

I've had a quick look around and it's not clear what that's all about. Any thoughts? When I say "recurring" I mean it fills my dmesg buffer.

Thanks for any thoughts.

eastpole

Re: dmesg full of usb messages

Did you ever figure this one out?  I'm getting the same issue.  from what I gather from the code, it looks to be errors coming out of the USB host controller that your ethernet adapter is connected to.  I have a feeling that this issue is related to the board electricals, as I've been soldering and resoldering pieces on odd places on my board.  Did you figure out a solution?


        /* serious "can't proceed" faults reported by the hardware */
        if (token & QTD_STS_HALT) {
                if (token & QTD_STS_BABBLE) {
                        /* FIXME "must" disable babbling device's port too */
                        status = -EOVERFLOW;
                } else if (token & QTD_STS_MMF) {
                        /* fs/ls interrupt xfer missed the complete-split */
                        status = -EPROTO;
                } else if (token & QTD_STS_DBE) {
                        status = (QTD_PID (token) == 1) /* IN ? */
                                ? -ENOSR  /* hc couldn't read data */
                                : -ECOMM; /* hc couldn't write data */
                } else if (token & QTD_STS_XACT) {
                        /* timeout, bad crc, wrong PID, etc; retried */
                        if (QTD_CERR (token))
                                status = -EPIPE;
                        else {
                                ehci_dbg (ehci, "devpath %s ep%d%s 3strikes\n",
                                        urb->dev->devpath,
                                        usb_pipeendpoint (urb->pipe),
                                        usb_pipein (urb->pipe) ? "in" : "out");
                                status = -EPROTO;
                        }

Re: dmesg full of usb messages

chiluk,
No, no solution and no progress here.

It's possible that the messages are coming from some electrical fault, but I have not opened my BB8's case or fired up a soldering gun near it. smile   My USB->Ethernet adapter is the Trendnet TU-ET100C.  This adapter is said to work on the Chumby platforms.

http://wiki.chumby.com/index.php/Chumby … d_Ethernet

Maybe you and I have similarly-broken Insignia Infocasts or similarly broken USB-Ethernet adapters? But no one else does?