[Bug 220069] [6.13.9] regression USB controller dies

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220069

--- Comment #10 from Claudio Wunder (cwunder@gnome.org) ---
> This means it's the "600 series chipset", which is reportedly a Promontory
> family chipset, made for AMD by ASMedia. And IME ASMedia controllers are
> pretty buggy.

That's interesting... I do recall on Windows at times, resuming from sleep
would.. have issues (I had to change the AMD drivers to custom ones due to
SMU/ULPS issues. I'm not sure if this piece of log `xhci_hcd 0000:03:00.2: xHC
error in resume, USBSTS 0x401, Reinit` is relevant.

> The debugfs dump will tell...

Never been so excited for a crash to happen lol.

> I think you said you have more of those logs, is the above always appearing a
> few seconds before "hc died"? It seems related to the 8-3 device, a VIA USB
> 3.0 hub.

For the sample of two items I have so far, it appears that these are showing
up. Note that on both the original regression and the current "apparent" one
(if we can even call it a regression?), these errors above are happening. I
will need to wait to see the next crash also happens to have said logs;

>  Were there no hardware changes, like USB devices added or moved to other
>  ports?

Nope, no changes. I know older versions of Fedora (40) had no issues, but it's
been a while since I've used it (I was recently on Windows 11 (no issues
whatsoever, except for AMDgpu ULPS driver issues) and now I've been fresh to
Bazzite (Universal Blue/Silverblue) and been facing said issues.

It could as well be _my hardware_ -- but given the coincidence, and that with
6.13.7 the issue disappeared for a whole week, and then once going to the next
update of Bazzite with 6.13.9 and the update with 6.14.3 it has been happening
again. (Curiously on 6.13.9 it happens not often, but on 6.14.3 it was
happening every few hours; Unfortunately since with rpm-ostree I rollbacked the
system, the logs for those boots are lost; I could attempt to upgrade to 6.14.3
to see if I find the bug more often)

That said, I genuinely don't know, nor if it is due to a Kernel change.

> IME such problems tend to be happening under particular workloads,

It happened before on both resuming from sleep, intensive workloads (i.e.
gaming) or simply when typing/using the PC normally or when the PC is idle. I
discarded power profile or power management at the time as a cause. Enabling or
disabling OS-managed ASPM also has no effect, so I ruled out being an ACPI/APM
issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.