Greg Kroah-Hartman has announced the release of the 6.19.10, 6.18.20, 6.12.78, 6.6.130, and 6.1.167 stable kernels. Each contains important fixes throughout the tree. Users are advised to upgrade.
AMDGPU page flip bug update Posted Mar 25, 2026 23:31 UTC (Wed) by Heretic_Blacksheep (guest, #169992) [Link] For those that are encountering the AMD GPU page/frame flip bug in the kernel since kernel version 6.12, the fix doesn't appear to have made it into mainline yet, assuming it's a single problem and this patch here https://lists.freedesktop.org/archives/amd-gfx/2026-Febru... fixes it. There seems to be a hardware work around as monitors connected with DisplayPort seem to be most likely to trigger the problem. The discussion is here: https://gitlab.freedesktop.org/drm/amd/-/work_items/3787 I have one game that will almost always trigger the problem, X4 Foundations. I'd stopped playing it for a while so I didn't know about the page flip bug till recently. This appears to be a separate problem than the laptop panel power management bug that's reported here: https://gitlab.freedesktop.org/drm/amd/-/work_items/4141 I'm not using, and don't own, a laptop with an AMD APU/iGPU so the panel power management issue probably isn't relevant in the middle of a game. My own setup is a desktop system with an AMD 5600X CPU, AMD 6650XT GPU connected to a LG 4k monitor with Adaptive Sync cranked down to 2156x1440 res instead of relying on Mint Cinnamon's rather... not useful... scaling via (normally) a DisplayPort cable. However, reading through the first GitLab issue suggested that DisplayPort link (re)negotiation might be triggering driver race conditions. Replacing the DP cable with a "dumb" HDMI cable at least appears to have stopped X4 Foundations from triggering the lock-up bug so far. Since I know the circumstances in X4 that triggers the lock-up I tried to force the situation with the HDMI cable instead and couldn't trigger the lock-up. Reports towards the bottom of the comments say 6.19.x is still affected. Kernel 6.8 used by earlier Mint 21 doesn't have this problem. If you installed 21 and just updated to 22, you can roll back to 6.8 or try the cable switch-out. 6.8 is still actively maintained, although it might be too old for the very latest hardware. I thought I'd drop this here in case anyone else with an AMD desktop is encountering the same problems and weren't aware of it being a known problem. I'm also wondering if this same problem isn't affecting the BSDs which use a ported version of the Linux AMDGPU driver. OpenBSD 7.8 just crashes when starting Xenocara (7.7 and earlier have never had a problem). FreeBSD 15.0 will eventually lock up in KDE 6.x/Wayland, but seems more stable with X.org. But it could be that KDE/X.org on FreeBSD just isn't triggering the race conditions but Wayland is. (Just guessing.)
Posted Mar 25, 2026 23:31 UTC (Wed) by Heretic_Blacksheep (guest, #169992) [Link]
There seems to be a hardware work around as monitors connected with DisplayPort seem to be most likely to trigger the problem. The discussion is here: https://gitlab.freedesktop.org/drm/amd/-/work_items/3787
I have one game that will almost always trigger the problem, X4 Foundations. I'd stopped playing it for a while so I didn't know about the page flip bug till recently. This appears to be a separate problem than the laptop panel power management bug that's reported here: https://gitlab.freedesktop.org/drm/amd/-/work_items/4141
I'm not using, and don't own, a laptop with an AMD APU/iGPU so the panel power management issue probably isn't relevant in the middle of a game. My own setup is a desktop system with an AMD 5600X CPU, AMD 6650XT GPU connected to a LG 4k monitor with Adaptive Sync cranked down to 2156x1440 res instead of relying on Mint Cinnamon's rather... not useful... scaling via (normally) a DisplayPort cable. However, reading through the first GitLab issue suggested that DisplayPort link (re)negotiation might be triggering driver race conditions. Replacing the DP cable with a "dumb" HDMI cable at least appears to have stopped X4 Foundations from triggering the lock-up bug so far. Since I know the circumstances in X4 that triggers the lock-up I tried to force the situation with the HDMI cable instead and couldn't trigger the lock-up. Reports towards the bottom of the comments say 6.19.x is still affected. Kernel 6.8 used by earlier Mint 21 doesn't have this problem. If you installed 21 and just updated to 22, you can roll back to 6.8 or try the cable switch-out. 6.8 is still actively maintained, although it might be too old for the very latest hardware.
I thought I'd drop this here in case anyone else with an AMD desktop is encountering the same problems and weren't aware of it being a known problem. I'm also wondering if this same problem isn't affecting the BSDs which use a ported version of the Linux AMDGPU driver. OpenBSD 7.8 just crashes when starting Xenocara (7.7 and earlier have never had a problem). FreeBSD 15.0 will eventually lock up in KDE 6.x/Wayland, but seems more stable with X.org. But it could be that KDE/X.org on FreeBSD just isn't triggering the race conditions but Wayland is. (Just guessing.)
Copyright © 2026, Eklektix, Inc. Comments and public postings are copyrighted by their creators. Linux is a registered trademark of Linus Torvalds
LWN