And now it just happened on 6.12.10 which is from mid-January. Specifically, after resuming from sleep. I also have two external monitors attached via TB4, so my setup pushes the limits of the chipset but that just means I trip on these things more often than people using only the laptop panel.
It clearly happens more often on 6.13.x versions but I’m not sure how far to go back to find a kernel version that works reliably. I’m sure this wasn’t happening in the fall.
Reading this and several other threads about this, I believe the issue is with Mesa-25, not the Kernel at all. I’m running Fedora 41, not Tumbleweed; however after downgrading to Mesa-24 I haven’t seen issues. But I also haven’t stressed the system enough to call it fixed.
As best I know there is no simple reproduction reported to the Mesa project at this time.
Thanks, Christopher. I disabled the various updates-testing repos and then sudo dnf distro-sync --allowerasing to get back to Mesa 24. I’ll let you know how it goes.
Personal advice
Skip 6.12 and 6.13 as possible, very buggy.
Screen issues, VM issues, ROCM doesn’t work.
Ise 6.10, 6.11 or some 6.14 kernels. 6.14 rc5 works good to me
I am yet another Tumbleweeder using Gnome+Wayland, also with a AMD Ryzen™ 5 7640U laptop. Thanks for the tip about kernel-longterm; I just installed it.
FYI, here are a couple of openSUSE bugzilla reports that I’ve been following as (perhaps) being related to our problem:
I notice that BIOS 3.07 has recently been released. Has anyone seen if it resolves any of this?
Thanks for the recap 
, I’ll keep an eye on those.
I installed 3.07 a few days ago and it didn’t change a thing. kernel-longterm is the only fix for me, at least it seems to be that way so far (zero freezes).
Kernel-longterm has also resolved the issue for me, at least for the past 24 hours. Also, the openSUSE bugzilla reports I mentioned above have been resolved without fixing our issue, so I’ve submitted a new one, 1239657 - Garbling screen artifacts after suspend/resume, specifically for what we’re seeing. Please add any additional information you may have. (It’ll show there are more than one person having the problem.)
I think I’ll hold off on 3.07 for now. No reason to roll too many dice at the same time. 
Using Arch Linux. Framework 16 on Linux 6.13.7
I downgraded packages that contained mesa or radeon in the name and were at version 25.x (specifically 25.0.1) to v24.
In my commandline I have amdgpu.dcdebugmask=0x10 amdgpu.gpu_recovery=1
So far I don’t see the amdgpu page fault citing firefox.
We’ll see. I won’t consider it a valid workaround yet but hopeful for now