AMD Linux Driver Bug Drops 3D Performance by 50% on RX 6000, RX 7000

A bug in AMD's Linux graphics drivers causes 3D performance to drop by over 50% on RX 6000 and RX 7000 series GPUs. Here is the workaround.

AMD Linux Driver Bug Drops 3D Performance by 50% on RX 6000, RX 7000

A recent code update to 's graphics drivers has triggered a severe performance crisis for users of RDNA 2 and RDNA 3 hardware. This bug causes 3D rendering and gaming frame rates to drop by more than 50 percent on affected systems. Linux users running newer kernel versions on RX 6000 or RX 7000 series cards should pause system updates immediately to avoid this degradation.

Users should pause system updates to avoid severe performance degradation

The issue stems from a memory leak prevention mechanism in the driver code that incorrectly locks and frequently resets critical video RAM resources. This error prevents the GPU from accessing the memory bandwidth required to sustain performance. The bug impacts all major recent Linux distributions, including Ubuntu 24.04 LTS, Fedora 40 and 41, Arch Linux, and Debian.

  • Affected Linux Distributions: Ubuntu 24.04 LTS, Fedora 40/41, Arch Linux, Debian
  • Affected GPU Architectures: RDNA 2 (RX 6000 series), RDNA 3 (RX 7000 series)
  • Performance Impact: 3D rendering and gaming performance dropped by over 50%
  • Root Cause: Memory leak prevention code incorrectly locked and reset critical VRAM resources

AMD is currently re-evaluating the problematic code and plans to release an emergency patch to fix the issue. The company has not yet specified the exact driver commit or kernel version that introduced the error. Until the fix arrives, the root cause remains a misapplication of memory management logic within the graphics stack.

Users can mitigate the performance loss by downgrading their Linux kernel to the previous stable version. Alternatively, delaying system updates will prevent the buggy driver from installing on affected machines. This workaround restores performance to normal levels while waiting for the official hotfix.

Discussion

0 comments

Log in to join the thread with a thoughtful take, question, or correction.

Add to the discussion