RX 6500 XT freezes the image after login

Help
1

I’ll post what I commented on here

Hi!

I have an RX 6500 XT and I see the same errors but in my case the entire image freezes and the signal is lost.

may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 0, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 1, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 2, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 3, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 4, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 5, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 6, async page read
may 26 00:28:22 woody kernel: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
may 26 00:28:22 woody kernel: Buffer I/O error on dev sr0, logical block 7, async page read
may 26 00:28:25 woody kernel: amdgpu 0000:0b:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000029 SMN_C2PMSG_82:0x00000000
may 26 00:28:25 woody kernel: amdgpu 0000:0b:00.0: amdgpu: Failed to retrieve enabled ppfeatures!
may 26 00:28:25 woody kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
may 26 00:28:28 woody kernel: amdgpu 0000:0b:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
may 26 00:28:30 woody kernel: amdgpu 0000:0b:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000029 SMN_C2PMSG_82:0x00000000
may 26 00:28:30 woody kernel: amdgpu 0000:0b:00.0: amdgpu: Failed to retrieve enabled ppfeatures!
may 26 00:28:31 woody kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:61:crtc-0] hw_done or flip_done timed out
may 26 00:28:34 woody kernel: amdgpu 0000:0b:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000029 SMN_C2PMSG_82:0x00000000

Hardware description:

  • CPU: AMD Ryzen 5 3600 6-Core Processor
  • GPU: Sapphire AMD Radeon RX 6500 XT
  • System Memory: 32GB DDR4
  • Display(s): 1080p
  • Type of Display Connection: DP

System information:

  • Distro name and Version: NixOS 25.05
  • Kernel version: 6.12.30
2

It’s an upstream issue, though there is a workaround. See this thread: Lockups with kernel 6.14.7 and AMD GPUs

1 Like
3

This is what I did for the workaround:

  boot.kernelParams = [
    "amd_iommu=on"
    "iommu=pt"
    "kvm_amd.npt=1"
    "kvm_amd.avic=1"
    "quiet"
    "splash"
    "microcode.amd_sha_check=off"
    "amdgpu.ppfeaturemask=0xfffdffff" # turned off Stutter Mode
    "amd_pstate=disable" # also disabled AMD's pstate
  ];

  # set the performance to manual after boot
  systemd.services.set-amd-power-settings = {
    enable = true;
    description = "Set AMD GPU power settings";
    wantedBy = [ "sysinit.target" ];
    serviceConfig = {
      Type = "oneshot";
      ExecStart = pkgs.writeShellScript "set-amd-power" ''
        echo "manual" > /sys/class/drm/card1/device/power_dpm_force_performance_level
        echo "1" > /sys/class/drm/card1/device/pp_power_profile_mode
      '';
    };
  };
4

You should probably figure out which of those changes actually helps; pstate is CPU related.

At the very least, to folks finding this from the internet, don’t blindly cargo cult that. And remove it when AMD fix their drivers.

1 Like