# AMD GPU MES Timeouts Causing System Hangs on Framework Laptop 13 (AMD AI 300 Series) **URL:** \ **Category:** Linux\ **Tags:** ubuntu\ **Created:** [June 30, 2025, 4:18pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364 "2025-06-30T16:18:25Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [July 8, 2025, 11:37am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/21 "2025-07-08T11:37:26Z")
This looks like what [11752c013f562a1124088a35bd314aa0e9f0e88f](https://github.com/torvalds/linux/commit/11752c013f562a1124088a35bd314aa0e9f0e88f) fixed, but that’s definitely already in your kernel. What is the version of your linux-firmware package? I want to double check how old the MES microcode is. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [July 8, 2025, 11:42am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/22 "2025-07-08T11:42:27Z")
Also besides the version of the linux firmware package can you also provide output for [amdgpu\_firmware\_info](https://docs.kernel.org/gpu/amdgpu/debugfs.html#amdgpu-firmware-info) from debugfs? ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [July 8, 2025, 7:21pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/23 "2025-07-08T19:21:39Z")
I hope to provide the correct information needed: dpkg -l gives me linux-firmware version 20240318.git3b128b60-0ubuntu2.14 /sys/kernel/debug/dri/0000:c1:00.0/amdgpu\_firmware\_info gives me: VCE feature version: 0, firmware version: 0x00000000 UVD feature version: 0, firmware version: 0x00000000 MC feature version: 0, firmware version: 0x00000000 ME feature version: 35, firmware version: 0x0000000b PFP feature version: 35, firmware version: 0x0000000d CE feature version: 0, firmware version: 0x00000000 RLC feature version: 1, firmware version: 0x11520400 RLC SRLC feature version: 0, firmware version: 0x00000000 RLC SRLG feature version: 0, firmware version: 0x00000000 RLC SRLS feature version: 0, firmware version: 0x00000000 RLCP feature version: 1, firmware version: 0x11520400 RLCV feature version: 0, firmware version: 0x00000000 MEC feature version: 35, firmware version: 0x0000000d IMU feature version: 0, firmware version: 0x0b342000 SOS feature version: 0, firmware version: 0x00000000 ASD feature version: 553648353, firmware version: 0x210000e1 TA XGMI feature version: 0x00000000, firmware version: 0x00000000 TA RAS feature version: 0x00000000, firmware version: 0x00000000 TA HDCP feature version: 0x00000000, firmware version: 0x17000041 TA DTM feature version: 0x00000000, firmware version: 0x12000016 TA RAP feature version: 0x00000000, firmware version: 0x00000000 TA SECUREDISPLAY feature version: 0x00000000, firmware version: 0x00000000 SMC feature version: 0, program: 11, firmware version: 0x0b650400 (101.4.0) SDMA0 feature version: 60, firmware version: 0x0000000c VCN feature version: 0, firmware version: 0x0711300d DMCU feature version: 0, firmware version: 0x00000000 DMCUB feature version: 0, firmware version: 0x09002400 TOC feature version: 0, firmware version: 0x0000000b MES\_KIQ feature version: 6, firmware version: 0x00000078 MES feature version: 1, firmware version: 0x00000062 VPE feature version: 60, firmware version: 0x0000000f VBIOS version: 113-STRIXEMU-001 And this might be worth mentioning: For productive use I use the generic kernel. It had the initial freeze problem. But that one is very rare. Linux jan-framwork13 6.11.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT\_DYNAMIC Thu Jun 26 14:16:59 UTC 2 x86\_64 x86\_64 x86\_64 GNU/Linux Under the OEM kernel I have the freeze isse very often. That is this kernel version: Linux jan-framwork13 6.14.0-1007-oem #7-Ubuntu SMP PREEMPT\_DYNAMIC Mon Jun 30 08:41:09 UTC 2025 x86\_64 x86\_64 x86\_64 GNU/Linux ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [July 8, 2025, 8:34pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/24 "2025-07-08T20:34:22Z")
Can you please try to upgrade the firmware binary manually from upstream linux-firmware? [gc\_11\_5\_0\_mes\_2.bin](https://gitlab.com/kernel-firmware/linux-firmware/-/blob/main/amdgpu/gc_11_5_0_mes_2.bin?ref_type=heads) Back up the old one in /lib/firmware/amdgpu and then replace with this one and rebuild your initramfs and reboot. If the old one is compressed you’ll need to compress this one too. When you’re rebooted check that debugfs file again to make sure that MES version has increased. ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [July 8, 2025, 10:06pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/25 "2025-07-08T22:06:45Z")
Here is what I did - just to make sure everything is correct: 1. wget [https://gitlab.com/kernel-firmware/linux-firmware/-/raw/main/amdgpu/gc\_11\_5\_0\_mes\_2.bin](https://gitlab.com/kernel-firmware/linux-firmware/-/raw/main/amdgpu/gc_11_5_0_mes_2.bin) 2. wget [https://gitlab.com/kernel-firmware/linux-firmware/-/raw/main/amdgpu/gc\_11\_5\_0\_mes\_2.bin](https://gitlab.com/kernel-firmware/linux-firmware/-/raw/main/amdgpu/gc_11_5_0_mes_2.bin) 3. sudo zstd gc\_11\_5\_0\_mes\_2.bin 4. sudo mv gc\_11\_5\_0\_mes\_2.bin.zst /lib/firmware/amdgpu/ 5. sudo update-initramfs -u 6. Rebooted But I still get these versions: MES\_KIQ feature version: 6, firmware version: 0x00000078 MES feature version: 1, firmware version: 0x00000062 ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [July 15, 2025, 11:57am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/26 "2025-07-15T11:57:34Z")
Any further ideas from anyone? I’m running on the generic kernel, because it is much more stable. (Just 1 or 2 crashes a week.) But I’d really like to fix this for a really stable system. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [July 22, 2025, 12:38am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/27 "2025-07-22T00:38:52Z")
Hmm; I’m not sure you updated properly. I just double checked on a Strix Framework 13 that I’m running all the latest firmware from linux-firmware.git. ```auto ❯ cat /sys/kernel/debug/dri/0/amdgpu_firmware_info | grep MES MES_KIQ feature version: 6, firmware version: 0x0000006d MES feature version: 1, firmware version: 0x00000074 ``` Here’s the checksums for all the GC 11.5.0 binaries, although granted my zstd compression in Arch might be different than you did. ```auto ❯ md5sum /lib/firmware/amdgpu/gc_11_5_0* 6d4e01ad0c42d32efa197d05d28ccc3e /lib/firmware/amdgpu/gc_11_5_0_imu.bin.zst da7ea6bfe2a75952f16b516962a1d0b7 /lib/firmware/amdgpu/gc_11_5_0_me.bin.zst 51076b7f3333f1abeb3dbc4cec43bf28 /lib/firmware/amdgpu/gc_11_5_0_mec.bin.zst 04acdceed64db6d2a520826bec0f0e15 /lib/firmware/amdgpu/gc_11_5_0_mes1.bin.zst e1934cf4e2ab511096cf3aec001042cd /lib/firmware/amdgpu/gc_11_5_0_mes_2.bin.zst 3cd20106fbde3882e364573195222bd0 /lib/firmware/amdgpu/gc_11_5_0_pfp.bin.zst 022eb948adefc47f8b71e113b0b96a97 /lib/firmware/amdgpu/gc_11_5_0_rlc.bin.zst ``` In short - try again, maybe you made a mistake along the way? ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [August 28, 2025, 10:24pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/28 "2025-08-28T22:24:27Z")
Sorry for the delay. I didn’t find the time to follow up. I tried again with the same steps and the same result. Next I tried with gc\_11\_5\_3 because I have the following files in /lib/firmware/amdgpu: ls -latr gc_mes\_2_ -rw-r–r-- 1 root root 50566 Jul 8 23:43 gc\_11\_5\_0\_mes\_2.bin.zst.backup -rw-r–r-- 1 root root 53618 Jul 15 18:59 gc\_11\_5\_3\_mes\_2.bin.zst -rw-r–r-- 1 root root 52066 Jul 15 18:59 gc\_11\_5\_2\_mes\_2.bin.zst -rw-r–r-- 1 root root 53624 Jul 15 18:59 gc\_11\_5\_1\_mes\_2.bin.zst -rw-r–r-- 1 root root 46957 Jul 15 18:59 gc\_11\_0\_4\_mes\_2.bin.zst -rw-r–r-- 1 root root 48101 Jul 15 18:59 gc\_11\_0\_3\_mes\_2.bin.zst -rw-r–r-- 1 root root 48056 Jul 15 18:59 gc\_11\_0\_2\_mes\_2.bin.zst -rw-r–r-- 1 root root 47929 Jul 15 18:59 gc\_11\_0\_1\_mes\_2.bin.zst -rw-r–r-- 1 root root 47093 Jul 15 18:59 gc\_11\_0\_0\_mes\_2.bin.zst -rw-rw-r-- 1 jan jan 59691 Aug 28 23:14 gc\_11\_5\_0\_mes\_2.bin.zst But this didn’t load the AMD firmware but resulted in a fallback mode. Do you have any additional idea here for me? Thanks! Jan ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [August 28, 2025, 11:00pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/29 "2025-08-28T23:00:34Z")
There is also an updated Linux firmware in proposed now as of a week ago. You can use that if you’re having a hard time with manually compressing ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [August 29, 2025, 6:29pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/30 "2025-08-29T18:29:30Z")
The firmware from propsed didn’t work either. The solution to get the firmware running was to replace all firmware files with the latest firmware version. I guess the update-initramfs did use one of the old versions for some reason. 3 hours later it seems to run stable with the OEM kernel. (Both AMD GPU and wlan.) Thanks for the help! Jan ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [August 31, 2025, 5:49am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/31 "2025-08-31T05:49:09Z")
Update: Even after this the system crashes. But now it takes a few hours not just a few minutes. @Mario_Limonciello It seems that I’m the only person with that issue, right? Could this be a hardware-isse instead of a firmware issue? ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [August 31, 2025, 12:03pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/32 "2025-08-31T12:03:35Z")
I will say there was an issue that was fixed by the updated microcode that could lead to graphics hangs which manifested as a micro engine scheduler time out. Assuming you upgraded properly now you should have the fix for it. If you want to double-check this you can get the firmware version info from debugfs (`/system/kernel/debug/dri/0/amdgpu_firmware_info`) and we can cross reference it against the headers of the latest version upstream to confirm. But as for whether your remaining timeout is hardware or not is a fuzzy line that’s really hard to identify from a stranger on the Internet with a single error message. Normally what needs to be done is the state of the graphics hardware be dumped and analyzed. In order to do that we need a solid reproducer. For example the MES timeout that was fixed was identified by a specific action in Blender even though it could also manifest in other uses of graphics shader. ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [August 31, 2025, 3:40pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/33 "2025-08-31T15:40:08Z")
I updated to the kernel and firmware from proposed - which didn’t fix the issue. And the problem is that there is no solid way to reproduce the error. It usually apperas while working with Vivaldi or Firefox browser - but other apps are cause the issue too. And there is no action within the browsers which causes the c rash every time. So unfortunately I only have the error message from the logs. Is there anything else I can do to track that issue? If no I’ll create a ticket and will as framework to replace the AMD GPU. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [August 31, 2025, 5:53pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/34 "2025-08-31T17:53:14Z")
Given you’re the only one reporting it I know of I think that’s a good idea. ---
**Author:** ![JL\_Framework](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jl_framework/32/28846_2.png) [@JL\_Framework](https://community.frame.work/u/JL_Framework)\ **Post date:** [September 3, 2025, 12:01am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/35 "2025-09-03T00:01:18Z")
    Hello. I think I may have the same problem - but the thread is long and I have not assimilated all of it. My problem is that LibreOffice Impress causes a really hard hang when using an HDMI external monitor. (I reported that problem [here](https://community.frame.work/t/fw13-amd-ui-freeze/64555/7) on this board. I have worked around the problem with a kernel boot switch.)     Cf. also [this problem](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-16-release-stable/73325/64), different but again involved with external monitors, and apparently caused by interaction between the kernel (well, some versions of it) and the very latest AMD F13 BIOS (which I have yet to install). ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [September 3, 2025, 1:20am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/36 "2025-09-03T01:20:13Z")
I already posted the solution to the Xorg hang in that bug. Switch off cinnamon in Xorg or apply the kernel patch. ---
**Author:** ![JL\_Framework](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jl_framework/32/28846_2.png) [@JL\_Framework](https://community.frame.work/u/JL_Framework)\ **Post date:** [September 3, 2025, 10:03am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/37 "2025-09-03T10:03:18Z")
I was not seeking help with the (bug that we can call) the xorg bug. Rather I was seeking to determine whether the following three problems are distinct. 1. The timeout bug that this the present thread treats. 2. The xorg problem that I have. 3. The problem that is partially caused by the new BIOS and that has to do with resolution on external monitors. I take it that each problem _is_ distinct. ---
**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\ **Post date:** [September 3, 2025, 11:28am UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/38 "2025-09-03T11:28:35Z")
1 and 2 should be distinct. 3 I don’t know. I would pick up the solution for 2 to decide. ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [September 4, 2025, 7:03pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/39 "2025-09-04T19:03:30Z")
I’m using LibreOffice Impress a lot including external monitors and had no issues with that. On my system it often apperaed with no screen attached at all (only the internal display). ---
**Author:** ![Jan\_Theofel](https://avatars.discourse-cdn.com/v4/letter/j/7cd45c/32.png) [@Jan\_Theofel](https://community.frame.work/u/Jan_Theofel)\ **Post date:** [October 16, 2025, 12:14pm UTC](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364/40 "2025-10-16T12:14:31Z")
After weeks of testing, it turned out **not to be a hardware fault** , but a software issue. Disabling PSR at the driver level stopped all GPU resets and display hangs. For anyone running into the same issue, create /etc/modprobe.d/amdgpu-disable-psr.conf with options amdgpu dcdebugmask=0x10 and rebuild initramfs — that completely eliminated the freezes on my system. The MES issue still exists, but it’s clearly unrelated — it wasn’t the trigger for these freezes. Hopefully a future firmware/kernel update will include an official fix so this workaround won’t be necessary anymore. [Previous page](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364.md?page=1) [Next page](https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364.md?page=3)