I was having some system problems with lots of audio popping / desktop stuttering that I tracked down to a bad PCIe usb card. After I removed it, most of the problems went away and there were significantly fewer errors cluttering my system journal. However I’m still seeing one particular error absolutely filling my journal (4 or 5 notifications every 5-15 seconds) with the following (the numbers before RXBD seem random to me):
May 12 22:41:14 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 144 RXBD info: -11
May 12 22:41:14 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 145 RXBD info: -11
May 12 22:41:20 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 151 RXBD info: -11
May 12 22:41:20 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 152 RXBD info: -11
May 12 22:41:22 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 240 RXBD info: -11
May 12 22:41:22 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 241 RXBD info: -11
It appears to be a problem with my WiFi adapter, which is built into my motherboard (Gigabyte X870E AORUS ELITE WIFI7 rev 1.2). Here’s the relevant output from lspci -k:
Which didn’t seem to make any difference. It’s hard to tell exactly what effect this error is having, perhaps some or all of the network instability I’ve been experiencing can be tied to this, or some of the occasional periodic audio stuttering that seems to line up with the journal entry timings.
Not saying this will solve your issue, but I have noticed some forum members having problems with their wifi chip while using the LTS kernel , and in some cases switching to the latest kernel (at the moment 6.14.6) solved their problem, maybe something to try , because your hardware seems rather recent.
Alright, I’ll give that a try tomorrow when I get off work. I was originally on the newest non-LTS kernel, but I switched to LTS when trying to sole my aforementioned stuttering problem, though it ended up being the hardware at fault. I never checked the system journal with the newer kernel though, so the WiFi may well have been fine there. I’ll report back tomorrow on the results.
Interesting. I’d like to avoid reinstalling if possible. It’s not that I can’t but I don’t want to get everything all set up again.
I did manage to catch another couple kinds of error out of the rtw89_8922ae driver, though I’m again not sure how to decipher their cause, let alone fix it.
Can not say this for sure but I think it might be a good thing to check your memory (sticks), the previous problems you had might have been a indication for memory problems also.
I could see that being the case. I’ve been burned plenty of times by memory’s XMP settings being right on the edge of stability. I havent had obvious memory problems since my latest hardware upgrade, but on my last system simply enabling XMP caused constant crashes or failures to start. Maybe I’ll try disabling the XMP and see if there’s any improvement.
Disabling XMP might help, but it could also be that the memory sticks have come loose a bit when installing or removing something. Sometimes seating the memory in different slots (if possible) might help. Or maybe even memory not being totally compatible with your CPU. Worst case scenario would be of course failing memory sticks.
As an update, I have reinstalled my OS with the latest EndeavorOS image, and all of my problems have been resolved, except for the original wifi drivers issue. I still see tons of
May 27 20:39:25 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 134 RXBD info: -11
May 27 20:39:25 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 135 RXBD info: -11
May 27 20:39:41 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 11 RXBD info: -11
May 27 20:39:41 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 12 RXBD info: -11
May 27 20:39:51 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 106 RXBD info: -11
May 27 20:39:51 desktop kernel: rtw89_8922ae 0000:11:00.0: failed to update 107 RXBD info: -11
messages in the system journal, even when running the newest 6.14.7-arch2-1 kernel.
I did find this issue from another user over on the Ubuntu forums with the exact same issue but on Ubuntu 24.04, so it definitely seems to be a linux kernel / kernel driver / kernel module thing rather than an endeavourOS/arch linux problem. Anyone familiar with how this issue could make it upstream to the correct maintainers?
