6.13.4 (and versions before it) atleast has a bug if you use flatpaks, it will crash/freeze the whole system when doing something inside the flatpak (for example uploading a file to flatpak app).
The GCVM_L2_PROTECTION_FAULT_status also happens to me on an up to date Fedora with kernel 6.13.4 when using Firefox (just occurred an hour ago while browsing LinkedIn)
I was able to reproduce most of this behavior on an AMD FW13, OpenSUSE Tumbleweed, KDE Plasma, 6.13.4 and also on 6.13.5. All on X11. Plasma freezing, blocky artifacts on the screen.
However, I do not have log entries like the ones OP pasted.
I do use Flatpaks though.
There were other issues with this board as well, see: USB C Error on boot – Framework has agreed to send me a new board, although I am skeptical that it’s a faulty board rather than a mix of kernel, driver, and BIOS issues.
I just had a hard freeze on 6.13.3, which I thought was immune. Happened while clicking a link in Firefox to open it in another tab. Firefox RPM, not flatpak.
Ctrl + Alt + F1 opened a TTY just fine, so it’s not like the entire system froze, just the graphics.
When trying to go back to the graphical session (on F7), all I could see was a message on the TTY - no way to go back to the DE. The message I saw is the one at the end of this excerpt (from sudo journalctl -k -b -1 | grep amdgpu):
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170302000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00340051
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x5
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x1
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170303000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170308000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170307000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170300000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080017030b000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080017030e000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080017030a000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170306000 from client 10
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:3 pasid:32806)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 1079915 thread firefox:cs0 pid 1079989)
Mar 05 15:01:05 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800170302000 from client 10
Mar 05 15:01:16 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
Mar 05 15:01:16 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
Mar 05 15:01:16 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=10771392, emitted seq=10771394
Mar 05 15:01:16 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Process information: process firefox pid 1079915 thread firefox:cs0 pid 1079989
Mar 05 15:01:16 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Mar 05 15:01:18 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=RESET
Mar 05 15:01:18 andromeda kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Mar 05 15:01:18 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: Ring gfx_0.0.0 reset failure
Mar 05 15:01:18 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Mar 05 15:01:20 andromeda kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Mar 05 15:01:20 andromeda kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:225
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:233
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:241
Mar 05 15:01:20 andromeda kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:249
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Mar 05 15:01:21 andromeda kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset(2) succeeded!
Mar 05 15:01:24 andromeda kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
I am on AMD FW 13, OpenSuse Tumpleweed, KDE Plasma (Wayland) as well, Kernel 6.13.5 now but I’ve also used 6.13.4 before. I’ve had a few minor stability issues over the last few weeks, but nothing major. Haven’t see blocky artifacts at all. Sometimes a temporary freeze in Firefox when interacting with a page, but just waiting fixed the issue for me. I haven’t looked at the logs at all, though. I’ll watch out for freezes and check the logs if I notice anything.
For folks on tumbleweed, I’m trying kernel-longterm since on 6.13.3 I’m also seeing intermittent freezes and since this is my main gear I can’t live with it.
Hoping this is a 6.13.x issue - kernel-longterm uses 6.12 for the moment. I’ve only been using it for a few minutes, so I can’t confirm it solves the problem.
More info here:
❯ uname -r
6.12.17-1-longterm
I think/hope you can do something similar on Fedora
FWIW 6.13.5-1-default behaves the same. Few minutes after resuming from suspend before artifacts start showing up, followed by whole session going down. dmesg:
kernel: amdgpu 0000:c1:00.0: amdgpu: in process steamwebhelper pid 22106 thread steamwebhe:cs0 pid 22110)
kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010ca07000 from client 10
kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:2 pasid:32781)
kernel: amdgpu 0000:c1:00.0: amdgpu: in process steamwebhelper pid 22106 thread steamwebhe:cs0 pid 22110)
kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010ca06000 from client 10
....
kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=30603, emitted seq=30605
kernel: amdgpu 0000:c1:00.0: amdgpu: Process information: process steamwebhelper pid 22106 thread steamwebhe:cs0 pid 22110
kernel: amdgpu 0000:c1:00.0: amdgpu: Starting gfx_0.0.0 ring reset
kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=RESET
kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
kernel: amdgpu 0000:c1:00.0: amdgpu: Ring gfx_0.0.0 reset failure
kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
PackageKit[22395]: get-updates transaction /14_dcaecbbb from uid 1000 finished with success after 3164ms
kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
Install a 6.12 or older kernel (might still be present)
Reboot to that kernel
Remove 6.13 packages dnf remove kernel*-6.13*
Add the following config to /etc/dnf/versionlock.toml:
version = "1.0"
[[packages]]
name = "kernel*"
comment = "Exclude 6.13 due to stability issues"
[[packages.conditions]]
key = "evr"
comparator = ">="
value = "6.14"
This will effectively blacklist kernel 6.13 and it’s friends, but still allow updates to 6.14 and higher
Just want to say that I have the same issue on Kernel 6.13.6, with openSUSE Tumbleweed + GNOME + Wayland on the Ryzen 5 7640U. I do also see the blocky artifacts on an external display. After the crash I get thrown out of my GDM session.
Unfortunately I just hit this problem on 6.12.15 as well. It doesn’t seem to be as frequent, but it still happens. I’ll probably try an earlier 6.12.x next.
)
