[ 0.003764] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20220331/tbfadt-615)
[ 1.906464] amdgpu 0000:c1:00.0: amdgpu: Fetched VBIOS from VFCT
Which Framework Laptop 13 model are you using? [Framework laptop 13 DIY (AMD Ryzen™ 7040 Series)]
After crashing when I start a new session I run “journalctl -b -1 -n 1000” and I get some errors like:
Feb 28 12:31:01 computer PackageKit[26541]: daemon quit
Feb 28 12:31:01 computer systemd[1]: Started anacron.service - Run anacron jobs.
Feb 28 12:31:01 computer systemd[1]: packagekit.service: Deactivated successfully.
Feb 28 12:31:01 computer anacron[26677]: Anacron 2.3 started on 2025-02-28
Feb 28 12:31:01 computer anacron[26677]: Normal exit (0 jobs run)
Feb 28 12:31:01 computer systemd[1]: anacron.service: Deactivated successfully.
Feb 28 12:33:55 computer gnome-shell[2443]: Window manager warning: Ping serial 8718796 was reused for window 0xa0003e, previous use was for window 0xa0005e.
Feb 28 12:34:00 computer google-chrome.desktop[3889]: [20668:20668:0228/123400.910051:ERROR:gles2_cmd_decoder_passthrough.cc(1082)] [GroupMarkerNotSet(crbug.com/242999)!:A000350AE4100000]Automatic fallback to s>
Feb 28 12:34:02 computer google-chrome.desktop[3889]: [3884:3911:0228/123402.006037:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
Feb 28 12:34:02 computer google-chrome.desktop[3889]: [3884:3911:0228/123402.006701:ERROR:registration_request.cc(305)] Registration HTTP response code not OK: 404
Feb 28 12:34:23 computer google-chrome.desktop[3889]: [3884:3911:0228/123423.496994:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
Feb 28 12:34:25 computer google-chrome.desktop[3889]: [3884:3911:0228/123425.750592:ERROR:registration_request.cc(305)] Registration HTTP response code not OK: 404
Feb 28 12:34:29 computer chrome[3884]: [3884:3906:0228/123429.054543:INFO:extension_garbage_collector.cc(184)] Garbage collection for extensions on file thread is complete.
Feb 28 12:34:32 computer kernel: [drm:gfx_v11_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
Feb 28 12:34:32 computer kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=664401, emitted seq=664404
Feb 28 12:34:32 computer kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2443 thread gnome-shel:cs0 pid 2464
Feb 28 12:34:32 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Feb 28 12:34:32 computer gnome-shell[2443]: amdgpu: The CS has been rejected (-125), but the context isn't robust.
Feb 28 12:34:32 computer gnome-shell[2443]: amdgpu: The process will be terminated.
Feb 28 12:34:32 computer kernel: amdgpu_cs_ioctl: 19 callbacks suppressed
Feb 28 12:34:32 computer kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:32 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:32 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:33 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:33 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:33 computer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
Feb 28 12:34:33 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 28 12:34:33 computer kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
Feb 28 12:34:33 computer kernel: [drm] PCIE GART of 512M enabled (table at 0x000000807FD00000).
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Feb 28 12:34:33 computer kernel: [drm] DMUB hardware initialized: version=0x08000500
Feb 28 12:34:33 computer kernel: [drm] kiq ring mec 3 pipe 1 q 0
Feb 28 12:34:33 computer kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 1
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 1
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: recover vram bo from shadow start
Feb 28 12:34:33 computer kernel: amdgpu 0000:c1:00.0: amdgpu: recover vram bo from shadow done
Feb 28 12:34:33 computer kernel: [drm] ring gfx_32785.1.1 was added
Feb 28 12:34:33 computer kernel: [drm] ring compute_32785.2.2 was added
Feb 28 12:34:33 computer gnome-shell[3346]: (EE) failed to write to Xwayland fd: Broken pipe
Feb 28 12:34:33 computer gnome-calendar[3395]: Error reading events from display: Broken pipe
While we only support Debian on a best effort basis, I’d like to see if we can potentially narrow down the cause of this for you.
I just have two questions to get us started: How much RAM does this system have? Have you tried the BIOS settings for adjusting RAM allocation to the iGPU?
You must use the latest kernel (6.12) from the Debian backports.
You must also update your “amdgpu” firmware from the Linux Firmware git.
I did it and have no issue so far.
Kernel 6.1 is not aware of your hardware.
I have not tried the BIOS settings for adjusting RAM allocation to the iGPU
I know Debian is not “officially supported” but I first tried with Ubuntu and it was having issues not booting so I tried Debian and it worked better for me, at least usable. But it is possible that the issue I had with Ubuntu is connected to the issue I am now having with Debian, hard to tell.
Ok, I can try that, after adding backports as described here Instructions I run “apt-cache search linux-image | grep 6.12” and I get:
linux-headers-6.12.12+bpo-amd64 - Header files for Linux 6.12.12+bpo-amd64
linux-headers-6.12.12+bpo-cloud-amd64 - Header files for Linux 6.12.12+bpo-cloud-amd64
linux-headers-6.12.12+bpo-rt-amd64 - Header files for Linux 6.12.12+bpo-rt-amd64
linux-headers-6.12.9+bpo-amd64 - Header files for Linux 6.12.9+bpo-amd64
linux-headers-6.12.9+bpo-cloud-amd64 - Header files for Linux 6.12.9+bpo-cloud-amd64
linux-headers-6.12.9+bpo-rt-amd64 - Header files for Linux 6.12.9+bpo-rt-amd64
linux-image-6.12.12+bpo-amd64-dbg - Debug symbols for linux-image-6.12.12+bpo-amd64
linux-image-6.12.12+bpo-amd64-unsigned - Linux 6.12 for 64-bit PCs
linux-image-6.12.12+bpo-cloud-amd64-dbg - Debug symbols for linux-image-6.12.12+bpo-cloud-amd64
linux-image-6.12.12+bpo-cloud-amd64-unsigned - Linux 6.12 for x86-64 cloud
linux-image-6.12.12+bpo-rt-amd64-dbg - Debug symbols for linux-image-6.12.12+bpo-rt-amd64
linux-image-6.12.12+bpo-rt-amd64-unsigned - Linux 6.12 for 64-bit PCs, PREEMPT_RT
linux-image-6.12.9+bpo-amd64-dbg - Debug symbols for linux-image-6.12.9+bpo-amd64
linux-image-6.12.9+bpo-amd64-unsigned - Linux 6.12 for 64-bit PCs
linux-image-6.12.9+bpo-cloud-amd64-dbg - Debug symbols for linux-image-6.12.9+bpo-cloud-amd64
linux-image-6.12.9+bpo-cloud-amd64-unsigned - Linux 6.12 for x86-64 cloud
linux-image-6.12.9+bpo-rt-amd64-dbg - Debug symbols for linux-image-6.12.9+bpo-rt-amd64
linux-image-6.12.9+bpo-rt-amd64-unsigned - Linux 6.12 for 64-bit PCs, PREEMPT_RT
linux-image-6.12.9+bpo-amd64 - Linux 6.12 for 64-bit PCs (signed)
linux-image-6.12.9+bpo-cloud-amd64 - Linux 6.12 for x86-64 cloud (signed)
linux-image-6.12.9+bpo-rt-amd64 - Linux 6.12 for 64-bit PCs (signed), PREEMPT_RT
Do you happen to know which of those could be a good fit?
Furthermore Debian-12 is generally a pretty outdated system. Debian series “testing” is usually in a state that most distros would call “stable”. Current Debian testing (v13, “trixie”) is very stable actually and is scheduled to be promoted to “stable” series this May, so @computer, I’d recommend you give it a try
Just install linux-image-amd64 from the backports, you will get the latest appropriate one. And it will then update to the latest one when a newer one is ready.
If you don’t want to update to a newer kernel, you can use linux-image-6.12.9+bpo-amd64
I had a crash again with latest kernel, so maybe the issue is related to the RAM? Could it be it not working properly? How can I run that adjusting RAM allocation?
Mar 04 09:47:22 computer systemd[2237]: Starting tracker-extract-3.service - Tracker metadata extractor...
Mar 04 09:47:22 computer dbus-daemon[2269]: [session uid=1000 pid=2269] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
Mar 04 09:47:22 computer systemd[2237]: Started tracker-extract-3.service - Tracker metadata extractor.
Mar 04 09:49:43 computer dbus-daemon[2269]: [session uid=1000 pid=2269] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.12' (uid=1000 pid=2364 comm="/usr/libexec/tracker-miner-fs-3")
Mar 04 09:49:43 computer systemd[2237]: Starting tracker-extract-3.service - Tracker metadata extractor...
Mar 04 09:49:43 computer dbus-daemon[2269]: [session uid=1000 pid=2269] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
Mar 04 09:49:43 computer systemd[2237]: Started tracker-extract-3.service - Tracker metadata extractor.
Mar 04 09:51:47 computer kernel: [drm:gfx_v11_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
Mar 04 09:51:47 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
Mar 04 09:51:47 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
Mar 04 09:51:47 computer kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=526797, emitted seq=526798
Mar 04 09:51:47 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Process information: process gnome-shell pid 2514 thread gnome-shel:cs0 pid 2535
Mar 04 09:51:47 computer google-chrome.desktop[5933]: [5972:5972:0304/095147.171863:ERROR:shared_context_state.cc(1383)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Mar 04 09:51:47 computer google-chrome.desktop[5933]: [5972:5972:0304/095147.172400:ERROR:gpu_service_impl.cc(1188)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B52
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x5
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B33
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=ADD_QUEUE
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B53
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x5
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x1
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: [drm:amdgpu_mes_map_legacy_queue [amdgpu]] *ERROR* failed to map legacy queue
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: failed to remap kgq
Mar 04 09:51:49 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
Mar 04 09:51:49 computer Logseq-linux-x64-0.10.9.AppImage[9255]: [9255:0304/095149.251685:ERROR:shared_context_state.cc(936)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Mar 04 09:51:49 computer Logseq-linux-x64-0.10.9.AppImage[9255]: [9255:0304/095149.251829:ERROR:gpu_service_impl.cc(1089)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Mar 04 09:51:51 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Mar 04 09:51:51 computer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Mar 04 09:51:51 computer kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Mar 04 09:51:51 computer kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
Mar 04 09:51:51 computer kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
Mar 04 09:51:51 computer kernel: [drm] PCIE GART of 512M enabled (table at 0x000000807FD00000).
Mar 04 09:51:51 computer kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Mar 04 09:51:51 computer kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Mar 04 09:51:51 computer kernel: [drm] kiq ring mec 3 pipe 1 q 0
I just want to start by thanking the other users because their suggestion that you want to be using a newer kernel where possible on our AMD mainboards is absolutely correct. Older versions of the amdgpu driver can have a variety of issues on newer GPUs. The various versions of kernel 6.12 have been a very mixed bag for our AMD devices and while some users report a smooth experience on some versions, others have nondescript amdgpu errors on the same versions.
The error you have there is unfortunately not super helpful beyond the crash likely being hardware acceleration related, which could be related to the amdgpu driver in the kernel or to AMD GPU related parts of the linux-firmware package which can be very difficult to track down. Errors identical to this have been observed even on desktop GPUs, both from AMD as well as Nvidia. It essentially means that a GPU process unrelated to the main rendering thread has crashed and is taking the rest of the driver with it. You can mitigate or workaround this issue by disabling hardware acceleration in-browser, but of course we would rather find fixes when we are able so users can get the most out of their hardware.
In a ticket, we might be able to pin this down to a specific bug that we can then work on a fix for. However, Debian is outside of the scope of our official support. Unfortunately this means the support work and troubleshooting would need to be done on an officially supported distribution for the hardware, such as Fedora 41 or Ubuntu 24.04.2, just to eliminate as many variables as possible for the process. I know this is suboptimal as it would be disruptive to your personal workflow, but it simplifies things in terms of reproducing the potential bug in question and getting a fix out.
I understand.
Thank you for your comment. I will for now try to disable hardware acceleration and if the error persists try with Fedora or Ubuntu again.
Did you update the firmware in /usr/lib/firmware/amdgpu/ , and then run “dracut --force” to rebuild the initrd file, and then reboot?
You must take the amdgpu firmware files from the Linux Firmware git.
