AMD GPU MES Timeouts Causing System Hangs on Framework Laptop 13 (AMD AI 300 Series)

Just want to contribute to this issue. I have had MES Ring Buffer issues while using certain apps on Fedora 43. My understanding is that there is a driver level issue with the Strix Point series.

Steps to reproduce: Download Komikuu flatpak and read your favorite comic (preferably really long ones)

  • Computer should start pulling a crazy amount of resources
  • Computer freeze

Run JournalCTL

Figured this information is likely useful to someone.

1 Like

Experiencing this on both Fedora 43 and Ubuntu 25.10 - in my case it seems to happen more frequently when youtube is open in Google Chrome. Going to try switching to Firefox for a bit to see if that is more stable but the driver shouldn’t be crashing regardless.

My latest crash was caused by an AMD GPU hang triggered by Chrome.

The sequence:

  1. Chrome’s GPU process caused a page fault in the AMD graphics driver (amdgpu)
  2. The GPU’s graphics ring (gfx_0.0.0) timed out
  3. The driver tried to reset the GPU but failed - MES failed to respond to msg=RESET
  4. The GPU ring reset failed completely

Key error lines:
amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32772)
amdgpu: Process chrome pid 4007 thread chrome:cs0 pid 4038
amdgpu: ring gfx_0.0.0 timeout
amdgpu: Ring gfx_0.0.0 reset failed

Experiencing this on NixOS on the Laptop 16 AI 300 with no dGPU.

Just experienced this for the first time on a Framework 13 with HX 370.

It was triggered at a time when loading a generic website page on Firefox.

amdgpu: MES failed to respond to msg=MISC (WAIT_REG_MEM)
amdgpu: failed to reg_write_reg_wait
amdgpu: MES ring buffer is full.

Just in case it helps anyone, and even though Jan_Theofel said way back in July 2025 that it didn’t help, I have had success with the amdgpu.sg_display=0 workaround.

I think one problem is the ā€œamdgpu: MES failed to respondā€¦ā€ message has a number of different causes.
For some causes, the amdgpu.sg_display=0 may help.
For others the amdgpu.cwsr_enable=0 may help.
or this one might just be something new.

Let me add my 50 cents to this; I think it’s not only a software issue but also hardware related.

I’m on an Asus Flow Z13, which I got as soon as they where available little under a year ago. I had the issues mentioned here, maybe once every 2-3 days. Annoying, but I figured firmware would be fixed at some point. Tried various boot parameters, with no real change to show for it.
Before New Years the laptop went in for RMA and when I got it back, they had replaced the motherboard. Now I’m having the issues as frequent as every 5 min. Making it almost unusable. Even if I roll back to a kernel and firmware from October or add all the suggested boot parameters. The issues remains.
The same kernel, firmware and laptop from last year, that crashed every 2-3 days, now crashes every 5 min. Only thing changed is the motherboard.

This indicates to me, that the issue is related to which batch/revision of GPU you have.
So we might have a situation, where the vendors and (AMD) developers are on a batch/revision that maybe never or rarely crashes and users might have one that crashes all the time.
Hence we’re seeing different solutions for different users and the real issue doesn’t get resolved.

I hope you’re wrong and you were just unlucky enough to get your laptop back after breaking change landed. I’m testing this patch now and god, I’m hopeful. Already running a workload that used to hand my laptop pretty quickly for over an hour already and its still stable.

It will take a while to get rid of the feeling that crash is about to happen when I click through web pages though.

Edit: nope. Still happens. I hope that it will fix the stability of system for at least few of you folks, I’m staying with my pretty expensive brick for now.

Folks who are still hitting this with the up to date linux-firmware, can you please come to this bug report Making sure you're not a bot!

It might help if someone can bisect.