Hi,
I’m on Slowroll and I’ve generally had a lot of stability issues on this machine; one message that keeps spamming journalctl hundreds of times a second and I’ve not really been able to make any traction on is as such:
xhci_hcd Frame ID 1773 (reg 14240, index 20) beyond range (1781, 627)
xhci_hcd Ignore frame ID field, use SIA bit instead
I’m asking here as honestly, I’m not entirely sure how to isolate the cause, or if it’s my hardware or a bug that should be reported somewhere. My knowledge of in-depth USB is limited to USB2 and simpler deices like HIDs.
I know there is an audio controller on the motherboard that has stuttering problems - but that seemed to be in part due to general kernel sluggishness and was made worse by graphics driver issues. So I stopped using it some time ago. I know I can unbind the driver but not sure if that would help here.
The log seems to be coming from the XHCI controller (I think, but not 100% how to tell) that PCI entry is the controller itself. But Previously I suspected a bad mouse cable as the messages seemed to appear when I moved it, but they’re now back in full force. So possibly it is the controller, except that should be built within the motherboard itself if it controls the back-panel audio too and I’m a bit surprised if that’s broken badly on pretty young hardware. Previously on ubuntu I did unplug the frontpanel as it seemed not to be working properly so that is out of the equation. This is one of those “PCSpecialist” machines who have the habit of twist-tying all the cables ridiculously tight inside the case, making it a massive nuisance for changing things but also risking damaging them. Would never buy one of those myself.
So USB all in seems to work okay but I am wondering if this is at the hardware level or if there’s somehting I can do about it at the OS level.
Given I’ve had so many issues I also was wondering if I was on a bad kernel - googling a lot of systemd entries finds others on different distros (e.g. Acrh) in a similar situation - they have sporadic journal entries come up, an update fixes it, then it resurfaces later, and it’s hard to pinpoint what is at fault. I was on 6.12-longterm
Does anyone have any advice at all please? Or would I need to break out wireshark, at which point it’s possibly not worth it and I’ll move onto the next problem.
Thanks