Hello!
I am getting this error:
Update your system/kernel to see if the problem persists.
Thank you for the reply, but the error exists since 41 and is not fixed by an updated.
Can confirm I’m having the same issue - seemed to have started from the latest kernel update (or amdgpu driver update). There was a discussion earlier from a user with a Nvidia gpu who seemed to be having a similar issue.
Have tried a few things but unsuccessful, i’m afraid.
Also using 42.
I have the same problem, there is a bug report here:
https://pagure.io/fedora-workstation/issue/463
Unfortunately nobody gave a solution yet.
Wait, It seems that the problem was mutter!!!
I tried downgrading mutter earlier (more of a wild guess than anything else), but obviously I didn’t do it right! Cheers!
For anyone else with this problem, the thread linked by @linuxkernel94 states this command as a possible fix (i.e. downgrading mutter):
sudo dnf in koji && cd $(mktemp -d) && pwd && koji download-build -a noarch -a $(uname -m) mutter-48.2-2.fc42 && sudo dnf in ./mutter-48.2-2.fc42.*.rpm ./mutter-common-48.2-2.fc42.noarch.rpm
Oh, and when it crashes changing the virtual console does not work. Also it happends more often when starting the system from standby but sometimes also during the running desktop enviroment. And i am using kde so mutter seems to not be installed, atleast dnf asks me if i want to install it when i type mutter in the shell (i dit not). Thank you!
To my surprise, this happened again today on my PC. I went to a friend’s house on christmas who runs Bazzite KDE (I use Silverblue 43), and he experienced the same issue that day.
He has a 7900 XT, while I’m using a 6600M. This is a serious problem, and it’s hard to believe it’s still happening in 2026.
Logs:
user@linux-pc:~$ journalctl -b -2 -p 3 --no-pager | grep -i amdgpu
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143605000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401031
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143603000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080014360d000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143607000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143600000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080014360b000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143602000 from client 0x1b (UTCL2)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32772)
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:11 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800143609000 from client 0x1b (UTCL2)
Jan 03 00:16:22 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 timeout, signaled seq=2677702, emitted seq=2677704
Jan 03 00:16:22 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:22 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.1.0 ring reset
Jan 03 00:16:22 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.1.0 reset succeeded
Jan 03 00:16:32 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 timeout, signaled seq=2677703, emitted seq=2677706
Jan 03 00:16:32 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process gnome-shell pid 4060 thread gnome-shel:cs0 pid 4117
Jan 03 00:16:32 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.1.0 ring reset
Jan 03 00:16:32 linux-pc kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.1.0 reset succeeded
Now it happened on my Laptop with AMD Vega 8 as well so It seems that this affects a lot if not all AMD devices, I have noticed that is issue mostly happens when using Kdenlive or an AI in the chromium based browser generating text (chatgpt, gemini,etc)
Do you have the Nvidias cuda drivers installed for hardware acceleration?
When it happens when using Kdenlive or an AI system generating texts it could mean it is caused by that. Can you test it with more programs which do intensive calculations to see if you can make it happen?
No, I don’t, also we are talking about websites like chatgpt, nothing using cuda. I can confirm this is a serious issue affecting a lot if not all AMD devices.
It most certainly does not affect all AMD GPUs. I have no issues with a Ryzen 7840U (with Radeon 780M graphics) or with a 9070XT. Both are running a fully updated Fedora 43 with KDE Plasma.
I have had amd gpu issues with every minor kernel at some point in the development. I started listing them there. I stopped maintaining the list at some point. The latest I blocked were 6.16.[567] and 6.18.3
I now have a 7600GT APU and some kernels are still causing hard lock. Last was 6.18.3. 6.18.4 and 6.18.5 are OK. At that time I had a R7 GPU,
It’s particular to specific kernels. If you’re experiencing issues, avoid that particular kernel.
For the record, I keep long term kernels all the time e.g. 6.12.xx
$ ls /lib/modules
6.12.25-200.fc42.x86_64 6.12.64-200.fc42.x86_64 6.12.65-200.fc42.x86_64 6.17.13-200.fc42.x86_64 6.18.4-100.fc42.x86_64 6.18.5-100.fc42.x86_64
My wife with her AMD gpu had the same problem right now, this is quite concerning, 4 different devices with fedora all the same issue, different Kernel versions, do you know if there is a way to avoid this permanently?
Hi all, I’m assuming this is a different issue now ti the original one I was experiencing back in July. I have an AMD 6700XT and this isn’t affecting me at all (on GNOME or Plasma). I also dual boot Fedora and Bazzite - both fine for me. The only difference is that I use Fedora 42, not 43.
Have you all tried running that command to downgrade mutter? It probably isn’t this, but if you haven’t tried it, it might be worth a shot:
sudo dnf in koji && cd $(mktemp -d) && pwd && koji download-build -a noarch -a $(uname -m) mutter-48.2-2.fc42 && sudo dnf in ./mutter-48.2-2.fc42.*.rpm ./mutter-common-48.2-2.fc42.noarch.rpm
Hi, I’ve been experiencing this issue since Fedora 40, but it has become significantly worse in Fedora 43. At this point, it’s the worst it has ever been. This problem affects not just me, but four different computers.
The error is always the same: a complete freeze or crash followed by a return to the login screen, and the logs are consistently identical. I’m genuinely surprised this doesn’t seem to be taken more seriously.
This situation reminds me of when I reported GNOME Shell memory leaks on Launchpad it took years before they were properly acknowledged. If Fedora offered an LTS kernel, I would switch immediately to it. I’d be really disappointed to have to leave Fedora over this issue alone 
A way to easily reproduce this error is to open a chat with chatgpt or gemini on a chromium browser, ask something and while It’s responding opening an image on Telegram.
Can you disable triple buffering in gnome, assuming it’s enabled, and still replicate this GPU driver crash?
Hi Steve I’m working on my own hardware and don’t want to risk damaging it, when this happens, I have to force a shutdown each time by pressing the power button, and I can’t afford to replace the device. I’ll try that approach and report back if it happens again.