To_Chi
March 30, 2025, 12:41pm
42
There do not appear to be any issues under Kernel 6.14/Mesa 25.0.1 in the Kubuntu 25.04 Beta.
I’ve spent an hour or so watching YouTube in Firefox under Wayland, having booted from the live USB.
Nothing from amd in the journal logs since start up, and it’s even fixed the previous stutter (https://bugzilla.mozilla.org/show_bug.cgi?id=1943836 )
$ uptime ; ps -efww|grep -i wayl ; uname -a ; dpkg -l|grep -i mesa
13:37:56 up 51 min, 2 users, load average: 0.59, 0.93, 0.86
kubuntu 4838 4581 0 12:46 tty1 00:00:00 startplasma-wayland
kubuntu 4865 1973 0 12:46 ? 00:00:00 /usr/bin/kwin_wayland_wrapper --xwayland
kubuntu 4874 4865 10 12:46 ? 00:05:30 /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority /run/user/1000/xauth_jQRaTS --xwayland
kubuntu 4958 4874 0 12:46 ? 00:00:00 /usr/bin/Xwayland :0 -auth /run/user/1000/xauth_jQRaTS -listenfd 8 -listenfd 9 -displayfd 80 -wm 82 -rootless
kubuntu 5346 1973 0 12:46 ? 00:00:00 /usr/bin/xwaylandvideobridge
kubuntu 11461 9751 0 13:37 pts/2 00:00:00 grep --color=auto -i wayl
Linux kubuntu 6.14.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Mon Mar 17 12:39:41 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
ii libegl-mesa0:amd64 25.0.1-2ubuntu2 amd64 free implementation of the EGL API -- Mesa vendor library
ii libgl1-mesa-dri:amd64 25.0.1-2ubuntu2 amd64 free implementation of the OpenGL API -- DRI modules
ii libglu1-mesa:amd64 9.0.2-1.1build1 amd64 Mesa OpenGL utility library (GLU)
ii libglx-mesa0:amd64 25.0.1-2ubuntu2 amd64 free implementation of the OpenGL API -- GLX vendor library
ii mesa-libgallium:amd64 25.0.1-2ubuntu2 amd64 shared infrastructure for Mesa drivers
ii mesa-utils 9.0.0-2 amd64 Miscellaneous Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 9.0.0-2 amd64 Miscellaneous Mesa utilities -- native applications
ii mesa-va-drivers:amd64 25.0.1-2ubuntu2 amd64 Mesa VA-API video acceleration drivers
ii mesa-vdpau-drivers:amd64 25.0.1-2ubuntu2 amd64 Mesa VDPAU video acceleration drivers
ii mesa-vulkan-drivers:amd64 25.0.1-2ubuntu2 amd64 Mesa Vulkan graphics drivers
kubuntu@kubuntu:~$
Adding another datapoint:
I’m seeing a very similar problem, though not identical(?), with a longer error log than before. I’m using two external displays, one connected by HDMI and the other by USB-C DP. I’ve had it happen two times in a row when closing Davinci Resolve (weird).
Here’s the new longer error message:
[ 215.277084] amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[ 215.277089] amdgpu 0000:c1:00.0: amdgpu: failed to remove hardware queue from MES, doorbell=0x1002
[ 215.277092] amdgpu 0000:c1:00.0: amdgpu: MES might be in unrecoverable state, issue a GPU reset
[ 215.277095] amdgpu 0000:c1:00.0: amdgpu: Failed to evict queue 1
[ 215.277186] amdgpu 0000:c1:00.0: amdgpu: Failed to evict process queues
[ 215.277187] amdgpu: Failed to quiesce KFD
[ 215.277392] amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
[ 215.277457] amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
[ 215.279749] amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
[ 218.340679] amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=SUSPEND
[ 218.340692] [drm:amdgpu_mes_suspend [amdgpu]] *ERROR* failed to suspend all gangs
[ 218.341264] amdgpu 0000:c1:00.0: amdgpu: suspend of IP block <mes_v11_0> failed -110
[ 221.638966] amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[ 221.638979] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[ 222.530108] gmc_v11_0_process_interrupt: 47 callbacks suppressed
[ 222.530118] amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0)
[ 222.530131] amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
[ 222.530139] amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B53
[ 222.530146] amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5)
[ 222.530152] amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
[ 222.530157] amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x1
[ 222.530162] amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x5
[ 222.530167] amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
[ 222.530172] amdgpu 0000:c1:00.0: amdgpu: RW: 0x1
[ 222.530190] amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0)
[ 222.530197] amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
[ 226.417894] usb 7-1: USB disconnect, device number 2
[ 226.537900] amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[ 226.537913] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[ 227.581130] usb 1-1: USB disconnect, device number 2
[ 228.542444] amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[ 228.542456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[ 228.544428] amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
[ 228.581270] amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
[ 228.581754] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
[ 228.581974] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[ 228.583822] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[ 228.589823] [drm] DMUB hardware initialized: version=0x08004D00
[ 228.612258] amdgpu 0000:c1:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
[ 229.028644] ucsi_acpi USBC000:00: unknown error 0
[ 229.028650] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 230.085690] usb 1-1: new full-speed USB device number 5 using xhci_hcd
[ 230.245131] usb 1-1: New USB device found, idVendor=32ac, idProduct=0002, bcdDevice= 0.00
[ 230.245138] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 230.245141] usb 1-1: Product: HDMI Expansion Card
[ 230.245143] usb 1-1: Manufacturer: Framework
[ 230.245145] usb 1-1: SerialNumber: 11AAAAAAAAAAAAAAAAAAAB00
[ 230.304745] hid-generic 0003:32AC:0002.000E: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[ 235.252629] amdgpu 0000:c1:00.0: [drm] enabling link 3 failed: 15
[ 235.507290] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1111: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
[ 235.531024] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1116: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
[ 235.556362] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1144: core_link_write_dpcd (DP_LINK_BW_SET) failed
[ 236.186438] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1111: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
[ 236.215319] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1116: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
[ 236.243008] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1144: core_link_write_dpcd (DP_LINK_BW_SET) failed
[ 236.815453] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1111: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
[ 236.836661] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1116: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
[ 236.857461] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1144: core_link_write_dpcd (DP_LINK_BW_SET) failed
[ 237.475987] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1111: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
[ 237.496856] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1116: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
[ 237.518494] amdgpu 0000:c1:00.0: [drm] *ERROR* dpcd_set_link_settings:1144: core_link_write_dpcd (DP_LINK_BW_SET) failed
[ 237.760302] amdgpu 0000:c1:00.0: [drm] enabling link 4 failed: 15
[ 237.816710] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 237.816714] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 237.816716] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 237.816718] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 237.816720] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 237.816722] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 237.816724] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 237.816725] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 237.816727] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 237.816729] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 237.816731] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[ 237.816734] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[ 237.816736] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[ 237.820012] amdgpu 0000:c1:00.0: amdgpu: GPU reset(1) succeeded!
At the end you can see that I was able to unplug the external displays and recover without rebooting. I did lose kwin though, which killed everything else.
package
version
Fedora
41
Mesa
25.0.2-2.fc41
amd-gpu-firmware
20250311-1.fc41
Kernel
6.13.8-200.fc41.x86_64
Kernel params
amdgpu.sg_display=0 amdgpu.dcdebugmask=0x210 mem_sleep_default=deep rtc_cmos.use_acpi_alarm=1
As far as Tumbleweed goes, this feels to be quite “stable” so far:
$ rpm -qa | grep -e kernel-default -e Mesa-2 | sort
kernel-default-6.13.7-1.1.x86_64
kernel-default-6.13.8-1.1.x86_64
Mesa-25.0.2-408.1.x86_64
$ uname -a
Linux carrack 6.13.8-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 24 08:31:14 UTC 2025 (7089702) x86_64 x86_64 x86_64 GNU/Linu
now if only mediatek wifi was equally stable.
edit:
it’s the latest avaialble snapshot:
$ grep VERSION_ID /etc/os-release
VERSION_ID="20250329"
1 Like
Tumbleweed has also been stable for me for the past few snapshots. I’m currently on snapshot 20250403 with kernel-default-6.14.0-1.1.x86_64 and Mesa-25.0.3-1699.413.pm.1.x86_64.
1 Like
I’ve had the video artifacts return, now, while on mesa version 24.3.4. So downgrading mesa is not a reliable fix for the problems.
This has been regularly happening to me on Fedora 42 for a few weeks now.
OS: Fedora Silverblue 42 (42.20250413.0)
Kernel: 6.14.2-300.fc42.x86_64
Mesa: 25.0.2-3.fc42.x86_64
amd-gpu-firmware: 20250311-1.fc42.noarch
kernel args: <disk-and-luks-setup> iommu=pt amd_iommu=on iommu=1 video=efifb:off
Kernel logs
huhti 15 15:17:08 marty-framework kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
huhti 15 15:17:08 marty-framework kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
huhti 15 15:17:08 marty-framework kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
huhti 15 16:56:11 marty-framework kernel: gmc_v11_0_process_interrupt: 122 callbacks suppressed
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:157 vmid:3 pasid:32780)
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800126a01000 from client 10
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x0030113A
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x5
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
huhti 15 16:56:11 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124601000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x0034115B
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x5
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x5
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x1
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x1
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124603000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124602000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124604000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124605000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124606000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124607000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124600000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124608000 from client 10
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:3 pasid:32780)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process thunderbird-bin pid 13732 thread thunderbir:cs0 pid 13805)
huhti 15 16:56:21 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800124609000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
huhti 15 16:56:37 marty-framework kernel: gmc_v11_0_process_interrupt: 7 callbacks suppressed
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:16 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800126e00000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601020
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x2
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601030
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601030
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32777)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 5268 thread firefox:cs0 pid 5360)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000080010c800000 from client 10
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x1
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
huhti 15 16:56:37 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
huhti 15 16:56:47 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
huhti 15 16:56:47 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
huhti 15 16:56:47 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1325143, emitted seq=1325144
huhti 15 16:56:47 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Process information: process gnome-shell pid 2188 thread gnome-shel:cs0 pid 2226
huhti 15 16:56:47 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Starting gfx_0.0.0 ring reset
huhti 15 16:56:49 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=RESET
huhti 15 16:56:49 marty-framework kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
huhti 15 16:56:49 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: Ring gfx_0.0.0 reset failure
huhti 15 16:56:49 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
huhti 15 16:56:49 marty-framework kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
huhti 15 16:56:49 marty-framework kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
huhti 15 16:56:52 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=SUSPEND
huhti 15 16:56:52 marty-framework kernel: [drm:amdgpu_mes_suspend [amdgpu]] *ERROR* failed to suspend all gangs
huhti 15 16:56:52 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: suspend of IP block <mes_v11_0> failed -110
huhti 15 16:56:54 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
huhti 15 16:56:54 marty-framework kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
huhti 15 16:56:54 marty-framework kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
huhti 15 16:56:54 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume
huhti 15 16:56:55 marty-framework kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
huhti 15 16:56:55 marty-framework kernel: [drm] VRAM is lost due to GPU reset!
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
huhti 15 16:56:55 marty-framework kernel: [drm] DMUB hardware initialized: version=0x08004D00
huhti 15 16:56:55 marty-framework kernel: thunderbolt 0000:c3:00.5: 0: failed to allocate DP resource for port 7
huhti 15 16:56:55 marty-framework kernel: [drm] DMUB HPD IRQ callback: link_index=5
huhti 15 16:56:55 marty-framework kernel: [drm] DMUB reported hpd status unchanged. link_index=5
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
huhti 15 16:56:55 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: GPU reset(4) succeeded!
huhti 15 16:56:57 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: VM memory stats for proc Xwayland(2953) task Xwayland:cs0(2899) is non-zero when fini
huhti 15 16:56:57 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: VM memory stats for proc (0) task (0) is non-zero when fini
huhti 15 16:56:57 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: VM memory stats for proc (0) task (0) is non-zero when fini
huhti 15 16:56:57 marty-framework kernel: rfkill: input handler enabled
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: wlp1s0: deauthenticating from 48:22:54:15:16:0d by local choice (Reason: 3=DEAUTH_LEAVING)
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
huhti 15 16:56:57 marty-framework kernel: PM: suspend entry (s2idle)
huhti 15 16:56:57 marty-framework kernel: Filesystems sync: 0.032 seconds
huhti 15 16:57:17 marty-framework kernel: Freezing user space processes
huhti 15 16:57:17 marty-framework kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
huhti 15 16:57:17 marty-framework kernel: [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR* wait_for_completion_timeout timeout!
huhti 15 16:57:17 marty-framework kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
huhti 15 16:57:17 marty-framework kernel: thunderbolt 0000:c3:00.5: 0:6 <-> 2:11 (DP): not active, tearing down
huhti 15 16:57:17 marty-framework kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
huhti 15 16:57:17 marty-framework kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
huhti 15 16:57:17 marty-framework kernel: [drm:amdgpu_dm_process_dmub_aux_transfer_sync [amdgpu]] *ERROR* wait_for_completion_timeout timeout!
huhti 15 16:57:17 marty-framework kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
huhti 15 16:57:17 marty-framework kernel: task:(sd-close) state:D stack:0 pid:71874 tgid:71874 ppid:1 task_flags:0x400040 flags:0x00000006
huhti 15 16:57:17 marty-framework kernel: Call Trace:
huhti 15 16:57:17 marty-framework kernel: <TASK>
huhti 15 16:57:17 marty-framework kernel: __schedule+0x2b6/0x630
huhti 15 16:57:17 marty-framework kernel: ? srso_alias_return_thunk+0x5/0xfbef5
huhti 15 16:57:17 marty-framework kernel: schedule+0x27/0xa0
huhti 15 16:57:17 marty-framework kernel: schedule_timeout+0xbf/0x100
huhti 15 16:57:17 marty-framework kernel: wait_for_completion+0x89/0x160
huhti 15 16:57:17 marty-framework kernel: __flush_work+0x277/0x3b0
huhti 15 16:57:17 marty-framework kernel: ? __pfx_wq_barrier_func+0x10/0x10
huhti 15 16:57:17 marty-framework kernel: drm_fb_release+0x166/0x190
huhti 15 16:57:17 marty-framework kernel: ? __pfx_drm_mode_rmfb_work_fn+0x10/0x10
huhti 15 16:57:17 marty-framework kernel: drm_file_free+0x1ae/0x270
huhti 15 16:57:17 marty-framework kernel: drm_release+0x5e/0xd0
huhti 15 16:57:17 marty-framework kernel: __fput+0xe3/0x2a0
huhti 15 16:57:17 marty-framework kernel: __x64_sys_close+0x3c/0x80
huhti 15 16:57:17 marty-framework kernel: do_syscall_64+0x7b/0x160
huhti 15 16:57:17 marty-framework kernel: ? srso_alias_return_thunk+0x5/0xfbef5
huhti 15 16:57:17 marty-framework kernel: ? do_user_addr_fault+0x36c/0x640
huhti 15 16:57:17 marty-framework kernel: ? srso_alias_return_thunk+0x5/0xfbef5
huhti 15 16:57:17 marty-framework kernel: ? exc_page_fault+0x7e/0x1a0
huhti 15 16:57:17 marty-framework kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
huhti 15 16:57:17 marty-framework kernel: RIP: 0033:0x7fb795581ae6
huhti 15 16:57:17 marty-framework kernel: RSP: 002b:00007fff86421f70 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
huhti 15 16:57:17 marty-framework kernel: RAX: ffffffffffffffda RBX: 00000000000000fc RCX: 00007fb795581ae6
huhti 15 16:57:17 marty-framework kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000000000fc
huhti 15 16:57:17 marty-framework kernel: RBP: 00007fff86421f90 R08: 0000000000000000 R09: 0000000000000000
huhti 15 16:57:17 marty-framework kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000411
huhti 15 16:57:17 marty-framework kernel: R13: 0000000000000000 R14: 0000000000000001 R15: 0000556145371b90
huhti 15 16:57:17 marty-framework kernel: </TASK>
huhti 15 16:57:17 marty-framework kernel: OOM killer enabled.
huhti 15 16:57:17 marty-framework kernel: Restarting tasks ... done.
huhti 15 16:57:17 marty-framework kernel: random: crng reseeded on system resumption
huhti 15 16:57:18 marty-framework kernel: PM: suspend exit
huhti 15 16:57:18 marty-framework kernel: PM: suspend entry (s2idle)
huhti 15 16:57:18 marty-framework kernel: amdgpu 0000:c1:00.0: amdgpu: VM memory stats for proc firefox(5360) task firefox:cs0(5268) is non-zero when fini
huhti 15 16:57:18 marty-framework kernel: Filesystems sync: 0.074 seconds
Was experiencing issues with instability in all mesa 25 versions though it had gotten better with mesa 25.0.3-1 it still wasn’t 100% fixed. Downgrading to 24.3.4-1 resolves it entirely for me. I am able to hibernate, sleep, open steam, play games and use my laptop as expected and not have it glitch out. This is after 24 hours of normal use for me so I think I’ll stick with a downgraded mesa until I hear its resolved.
1 Like
quaff
April 18, 2025, 6:08pm
49
I’m running KDE Plasma 6.3.4, Arch Linux, 6.14.2-arch1-1 kernel, Framework 13 AMD Ryzen 7 7840U. The issue experiencing is when on battery, and I have my sleep set to Hybrid, after waking up from hybrid sleep, my screen is black and the mouse cursor is a block artifact. Which forces me to have to hard reboot.
I have the kernel parameter amdgpu.dcdebugmask=0x10 set. I’m also using a swapfile partition that’s on my root LUKS enabled partition. Not sure if that’s related. But something tells me it could be since memory sleep works but disk sleep seemingly doesn’t.
EDIT: Here’s an image of the mouse cursor artifact:
Interesting. I have a couple differences in my setup compared to yours that might help you isolate the problem. I do not use that kernal parameter e.g.
[user@cogsworth ~]$ cat /proc/cmdline
initrd=\#################\6.14.2-arch1-1\initrd nvme_load=YES nowatchdog rw rd.luks.uuid= root=/dev/mapper/luks-################# rd
.luks.uuid=################# resume=/dev/mapper/luks-################# systemd.machine_id=#################
I also do not use a swap file but use a swap partition. So maybe it could be either of those things causing the issue. I also have my GPU setting in my bios set to the game mode so it has more shared ram though Im not sure if that will make any difference either
I’ve been using 25.0.4 since yesterday since it includes this commit:
It should be fixed now theoretically.
3 Likes
I’ve been using 25.04 since it came out and there is still no updated packages from apt regarding kernel/mesa. And I’m experiencing these amdgpu crashes
I’m not talking about Ubuntu at all.
I am using Mesa (and related packages like radeon vulkan etc) v25.0.4 on my Arch Linux system.
Ubuntu is behind I imagine
1 Like
hah I’m so sorry about the confusion!
quaff
April 22, 2025, 2:41pm
55
I’m on arch, same packages. Still experiencing the issue.
Atemu @Atemu
Not able to repro with 25.0.4 anymore.
If you are still able to repro on that version, you have a different issue, so please report it separately.
From the issue mentioned before
1 Like
Looks good to me, too.
I’ll ask mods to solve this.
