On Sat, Jan 23, 2021 at 11:14:19AM +0100, Stanislaw Gruszka wrote: > On Fri, Jan 22, 2021 at 05:00:21PM +0200, Mathias Nyman wrote: > > >> Or is this due to the specific host controller device hardware? Should > > >> this be a xhci quirk for a specific pci device instead? > > > > Exactly, this should be checked. > > Stanislaw, weren't there a few users already that saw this issue? > > There are 30+ users cc-ed in the bugzilla report. However I think some > of them are not affected by issue originally reported by Bernhard. > They just saw "WARN Set TR Deq Ptr cmd failed due to incorrect slot > or ep state" message caused by different problem and added comment > to this particular bug report. > > > Do we know what xHCI controllers they were using? > > What I can tell issue was reported mostly on ASMedia and AMD > controllers. We can ask for exact vendor and device IDs and > just add xhci->quirks flag. > > However I'm not entirely sure that xHCI hardware misbehave > is actual root cause. I think equally probable is that > connected device do not handle soft retry correctly. In that > case disabling Soft Retry per device would be actually > "lightest hammer" since other devices connected to the > xHCI host could benefit from faster recovery. > > Is there way to debug/identify which side: host or device > hardware misbehave when Soft Retry is performed ? So I think we do not have such possibility. If xhci quirk is something that can be accepted I'll precede with such patch. I'm going to ask bug reporters about xHCI conntroler PCI-id's ... Stanislaw
