this post was submitted on 06 Jan 2026
48 points (98.0% liked)
Linux Gaming
23047 readers
249 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hmm. If you don't mind sharing, when you hit the problem, were you concurrently running a video game and an LLM on the card? That seems to be what the guy there was doing.
Nope, just running the game. But I am running kde with a lot of fancy shit on and I'm switching kernels around and they all have the same issue. I might need to do my own issue. Tried, 6.18-zen,6.17-hardened, 6.12-lts. I'll try a few more kernels tomorrow but I'm a bit stumped
Hmm. Kinda a long shot, but if it's easy to reproduce and you're looking for switches to try throwing, the amdgpu driver does have a number of options.
Might try rebooting, and at GRUB, editing the kernel command line, and disabling some features, seeing if things magically go away.
Like, the bug report there is talking about some ring timeout. Maybe irrelevant, but could try amdgpu.async_gfx_ring=0 on the kernel command line.
Hey, posted the issue! Got moved to to the mesa issue board. Here's the issue if you're curious https://gitlab.freedesktop.org/mesa/mesa/-/issues/14617
Greatly appreciated! I'll give it a shot and build that issue on the amd issue tracker.