Linux 7.2 Reverts DRM Scheduler Change After Serious GPU Regressions

Linux kernel developers made a significant last-minute graphics change for Linux 7.2, reverting the DRM GPU scheduler back to its previous FIFO policy by default after the newer fair scheduling implementation caused serious performance regressions. The revert was submitted just before the final Linux 7.2 release after users reported severe slowdowns and desktop freezes under sustained GPU workloads.
The decision demonstrates the kernel community’s conservative approach to regressions: when a new feature causes problems this late in a development cycle, restoring known-good behavior can be safer than rushing an incomplete fix.
What Changed in Linux 7.2?
Earlier in the Linux 7.2 development cycle, the DRM subsystem switched its default GPU scheduling policy to a new fair scheduler.
The goal was to distribute GPU execution time more fairly between competing workloads. Instead of relying on the established FIFO scheduling behavior, the new implementation uses a fairness-oriented approach designed to prevent one workload from dominating GPU resources.
However, real-world testing exposed problems that had not appeared during earlier development.
The final DRM fixes for Linux 7.2 therefore:
- Revert the fair scheduler changes
- Restore FIFO as the default
- Restore selectable scheduling policies
- Mark the fair scheduling policy as experimental
DRM maintainer Dave Airlie acknowledged that developers may have moved too aggressively when switching to the new scheduler.
AMD Radeon Gaming Exposed the Regression
The problem became particularly noticeable during gaming on an AMD Radeon RX 9070 XT.
A regression report described severe performance degradation when the GPU remained close to 100% utilization. A game running through Proton could drop to roughly 10 FPS or freeze, while audio continued playing normally.
The problem could become severe enough that the entire KDE Plasma Wayland session stopped responding, sometimes requiring the compositor to be killed or the computer to be rebooted.
Interestingly, reducing GPU load—such as by opening an in-game menu or switching away from the game—could immediately stop the stuttering.
FIFO Worked, FAIR Did Not
Testing provided strong evidence that the new scheduling policy was responsible.
The reporter compared Linux 7.2 release candidates using FAIR against configurations using the previous FIFO policy. Under otherwise similar conditions:
FAIR: reproduced the performance problem.
FIFO: survived extended stress testing without the regression.
Linux 7.1.x also behaved normally.









