On 3.12.2023 10.38, Greg KH wrote:
On Sun, Dec 03, 2023 at 03:32:52AM -0500, Kris Karas (Bug Reporting) wrote:
Greg KH wrote:
Thanks for testing, any chance you can try 6.6.4-rc1? Or wait a few
hours for me to release 6.6.4 if you don't want to mess with a -rc
release.
As I mentioned to Greg off-list (to save wasting other peoples' bandwidth),
I couldn't find 6.6.4-rc1. Looking in wrong git tree? But 6.6.4 is now
out, which I have tested and am running at the moment, albeit with the
problem commit from 6.6.2 backed out.
There is no change with respect to this bug. The problematic patch
introduced in 6.6.2 was neither reverted nor amended. The "opcode 0x0c03
failed" lines to the kernel log continue to be present.
Also, is this showing up in 6.7-rc3? If so, that would be a big help in
tracking this down.
The bug shows up in 6.7-rc3 as well, exactly as it does here in 6.6.2+ and
in 6.1.63+. The problematic patch bisected earlier appears identically (and
seems to have been introduced simultaneously) in these recent releases.
Ok, in a way, this is good as that means I haven't missed a fix, but bad
in that this does affect everyone more.
So let's start over, you found the offending commit, and nothing has
fixed it, so what do we do? xhci/amd developers, any ideas?
thanks,
greg k-h
I suggest reverting these two patches from everywhere (all stable):
a5d6264b638e xhci: Enable RPM on controllers that support low-power states
4baf12181509 xhci: Loosen RPM as default policy to cover for AMD xHC 1.1
Then write a new well tested patch that adds default runtime pm to those AMD
hosts that support it. And only add that to usb-next
-Mathias
