Or could there be something wrong in the low level USB driver (Cadence in our case)? We need to figure out why we Is this the expected behavior when USB transaction error happens for all transfers when using cdc-acm class driver? That loop is to either unbind the usb driver or power cycle the board. Transfers continues despite there is nothing on the USB bus any longer. If I pull the reset pin of the USB hub and keep it in reset state at this point, the event loop of failing The SoC almost becomes unresponsive since it spends most of the This loop of failing transfers seems to continue until we either unbind This behavior generates a lot of events on the event ring which causes Like xhci resets the ep, sets TR Deq Ptr to unstall the ep and then a new transfer is started (-EPROTO which in xhci translates to 'USB transaction error"). If I enable dynamic debug on xhci_hcd and cdc-acm I can see that all transfers have error code -71 This often leads to RCU stalls and sometimes Kernel panics. In the terminal indicating that the xhci event ring is full. When this happens we get a lot of "xhci-cdns3: ERROR unknown event type 37" It is likely that the modem is misbehaving. Sometimes we end up in a situation where all transfers over USB generetes 'USB transaction Errors". The modem presents it self as a cdc-acm device with 4 tty:s. There is a modem connected to the SoC via USB through a USB hub. We are running Linux 4.19.35 from NXP on the SoC. 16:39 ` Greg KH 0 siblings, 1 reply 25+ messages in threadįrom: Jonas Karlsson 15:05 UTC ( / raw) USB transaction errors causing RCU stalls and kernel panics All of help / color / mirror / Atom feed * USB transaction errors causing RCU stalls and kernel panics 15:05 Jonas Karlsson
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |