> On 20-03-09 14:21:56, Jonas Karlsson wrote: > > > > > > If autosuspend is suspicious, Jonas, could you please try to disable > > > autosuspend for all USB devices (including the roothub and controller) to see > what happens? > > > > > > Peter > > > > I have run some tests with autosuspend turned off by doing this: > > for i in $(find /sys -name control | grep usb);do echo on > $i;echo > > "echo on > $i";done; > > > > To make our modem misbehave we need to cool it down in a temp chamber > > which I haven't had access to the past days. However we have found two > > other ways to reproduce the event storm causing event ring full > > messages spamming the logs. The pattern in the attached file repeats itself > until I unbind the driver. > > Hi Jonas, > > Do you have below commit at your local tree? If you have, I am puzzled why you > still get "Event Ring Full Error" error, maybe Mathias have the answer? > > commit dc0ffbea5729a3abafa577ebfce87f18b79e294b > Author: Peter Chen <peter.chen@xxxxxxx> > Date: Fri Nov 15 18:50:00 2019 +0200 > > usb: host: xhci: update event ring dequeue pointer on purpose > Yes, I have applied that commit. The logs I have attached so far have had that commit applied. It reduces the amount of Unknown event type 37 messages significantly. > @Mathias, could xhci design some software retry limits for transaction error? It > may avoid retry storm due to hardware issue (eg, signal issue). For EHCI, there is > a design to define QH_XACTERR_MAX at qh_completions for that. > > Peter
