Hi Mathias On Mon, Dec 16, 2019 at 5:27 AM Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> wrote: > > Hi Prashant > > On 5.12.2019 22.34, Prashant Malani wrote: > > Hi Mathias and Bernhard, > > > > I was interested in knowing if this issue was resolved (sounded like > > this was deemed to be a hardware error, but I'm not sure). > > The reason I ask is that we've recently noticed a similar error > > popping up while using Realtek rtl8153a-based ethernet USB dongles > > (these use the r8152 driver) on kernel 4.19 : > > " hci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to > > incorrect slot or ep state." > > This is generally followed by the dongle getting reset, and the > > process repeats itself continuously. > > Sorry about the delay, your traces show a transaction error, and the port link > going to inactive error state. > > xhci driver tries to recover from the transaction error with a soft retry > (endpoint reset), while hub thread will need to reset the whole device to recover > from the inactive link error state. > > Can you try reverting commit: > "f8f80be501aa xhci: Use soft retry to recover faster from transaction errors" > > If you still see "Transfer error for slot x ep y on endpoint" in dmesg, > but device is not reset and works normally, then it's possible that the soft retry > makes things worse. Thanks for your analysis, and sorry for the delayed response. I reverted the aforementioned commit. While the transfer error no longer appears, I still see the repeated resets, so there is likely an issue either on the Host Controller, or the device firmware itself. I'll continue digging, but seems safe to rule out soft retry as a culprit. Best regards, > > If not, then the transaction error and the link inactive error are most likely symptoms > of some other cause. > > The hci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state." > is as in Bernhard's case due to xhci driver trying to issue a command for a slot in context error > state, this part needs to be fixed in the driver, but should not matter much. Device must be reset > anyway to recover from the link inactive error state. > > -Mathias >
