Serious graphical stability issues after suspend/hibernate on 6.13.7

Which Linux distro are you using?

Arch

(If rolling release, last date updated?)

Today

Which kernel are you using?

6.13.7

Which BIOS version are you using?

3.05

Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen™ 7040

Symptoms: Graphical artifacts, graphics crash/freeze (though it seems not to be a hard lockup)

dmesg output:

Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000000000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401E11
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          Faulty UTCL2 client ID: GCR (0xf)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          MORE_FAULTS: 0x1
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          PERMISSION_FAULTS: 0x1
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          RW: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000000000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401E11
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          Faulty UTCL2 client ID: GCR (0xf)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          MORE_FAULTS: 0x1
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          PERMISSION_FAULTS: 0x1
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:          RW: 0x0
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000001000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000001000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000002000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000002000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000003000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000003000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000004000 from client 10
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:8 vmid:4 pasid:32772)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:  in process kwin_wayland pid 1529 thread kwin_wayla:cs0 pid 1579)
Mar 23 14:04:41 Framework kernel: amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x0000800000004000 from client 10

/cc @Mario_Limonciello

You should report this to mesa.

Thanks @Mario_Limonciello, this looks similar? [amdgpu] Heavy artifacting in desktop applications since bump from 24.3.4 to 25.0.1 (#12809) · Issues · Mesa / mesa · GitLab

Yeah looks potentially the case. Try downgrading mesa and see if things improve. If they do; you can try to assist mesa upstream by bisecting mesa.

1 Like

This also looks close.