Fedora 39 KDE & AMD RX 7800 XT & Kernel 6.7.3 - Monitor goes into sleep mode when rebooting

Actually, I have the same issue I have in Fedora 40 Rawhide with kernel 6.8.x (https://discussion.fedoraproject.org/t/fedora-40-rawhide-black-screen-after-rebooting-with-kernel-6-8-rc/) in Fedora 39 now after installing kernel 6.7.3.

Some days ago, I created a backup of my Fedora 39 installation. Today I restored this backup. Till kernel 6.6.13 installed, everything worked fine. After restoring Fedora 39 backup, some system updates had to be installed. Also, kernel updated to 6.7.3, and now I’m not able to restart my system without issue.

There seems to be an issue in connection to kernel 6.7.x (and above) and an AMD RX 7800 XT graphics card. Don’t know if it is the same with RX 7900 XT, but I think so. And it isn’t a specific Fedora issue. When rebooting, the monitor goes into sleep mode. There is no way to wake it up again by pressing keys. In the background, it seems that the OS is booting up. So it would be possible to log into the system without seeing anything. Pressing the power button shuts down the computer. Turning it on again and the boot screen is visible and also the login screen appears. Everything is working until the next reboot.

So, the only solution to prevent the monitor going to sleep is shutting down the computer when a reboot is needed.

The same issue appeared in Nobara 39 when kernel 6.7.0-200 was available and installed. The developer was able to fix this issue by himself. With kernel 6.7.0-204 installed, the issue is fixed in Nobara 39. (See: Discord )

Now I switched back to kernel 6.6.13 in Grub menu to be able to reboot my system if needed.

Here is the output of inxi -Fz. I hope it helps to find a solution?

System:
  Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.27.10 Distro: Fedora release 39 (Thirty Nine)
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570 TOMAHAWK WIFI (MS-7C84)
    v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.F0
    date: 10/12/2023
CPU:
  Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP cache:
    L2: 6 MiB
  Speed (MHz): avg: 2336 min/max: 2200/4672 cores: 1: 2054 2: 2049 3: 2200
    4: 2200 5: 2200 6: 3800 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200
    13: 2038 14: 2031 15: 4515 16: 2200 17: 2200 18: 2200 19: 2200 20: 2200
    21: 2200 22: 2199 23: 2200 24: 2200
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.4
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    resolution: 3440x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.3 renderer: AMD
    Radeon RX 7800 XT (radeonsi navi32 LLVM 17.0.6 DRM 3.54
    6.6.13-200.fc39.x86_64)
  API: Vulkan v: 1.3.268 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel
  API: ALSA v: k6.6.13-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: active
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  IF: enp38s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.2
Drives:
  Local Storage: total: 7.51 TiB used: 2.65 TiB (35.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB
  ID-3: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
  ID-4: /dev/sdb vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB
  ID-5: /dev/sdc vendor: Seagate model: ST2000DM001-1CH164 size: 1.82 TiB
  ID-6: /dev/sdd vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB
Partition:
  ID-1: / size: 929.93 GiB used: 30.85 GiB (3.3%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 352 MiB (36.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 929.93 GiB used: 30.85 GiB (3.3%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 1
Info:
  Processes: 715 Uptime: 18m Memory: total: 32 GiB available: 31.26 GiB
  used: 4.39 GiB (14.1%) Shell: Bash inxi: 3.3.31

What else do you need that I can provide here?

1 Like

The 6.7 kernel is in testing suggest you raise a bug ticket against the kernel with the information you posted here.

2 Likes

I don’t know how to raise such a ticket … :confused:

Start here Using Bugzilla :: Fedora Docs if you need more help please ask

1 Like

I found a bug report, created an account and answered.

https://bugzilla.redhat.com/show_bug.cgi?id=2262577

Hopefully this will fix my issue, too. Thanks for helping, @barryascott ! :slight_smile:

The 6.7 kernel is no longer in testing.

Yes, I know.

Actually, I’m using kernel 6.6.14 and excluded kernel from updating. 6.7.3 and 6.7.4 are still having this issue. Let’s see when it will be fixed.

Ooof!

I just got my new 7800xt having RMA’d a new 7700xt after experiencing this reboot hang issue.

I presumed the 7700 was haunted as it was from the outlet and my 6600xt didn’t have the same issue.

Ah well. Now I have a better GPU. Guess I’ll be shutting down instead of rebooting for the foreseeable.

Thanks for raising the bugs!

1 Like

Yesterday, I updated to Kernel-Fsync 6.7.4 from Copr. It has some patches integrated for gaming and doesn’t have this reboot issue.

https://copr.fedorainfracloud.org/coprs/sentry/kernel-fsync/

Actually, it looks fine for me with this kernel. Just had to disable Secure Boot in UEFI.

1 Like

With the Fedora 6.7.4-200 I see the reboot issue. When I ssh into the PC I see lots of panics in dmegs, here is the first I see:

[  +0.030707] snd_hda_intel 0000:08:00.1: bound 0000:08:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[  +0.030130] NET: Registered PF_QIPCRTR protocol family
[  +0.233380] [drm] kiq ring mec 3 pipe 1 q 0
[  +0.247858] amdgpu 0000:08:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring mes_kiq_3.1.0 test failed (-110)
[  +0.000243] [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed
[  +0.000205] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v11_0> failed -110
[  +0.000157] amdgpu 0000:08:00.0: amdgpu: amdgpu_device_ip_init failed
[  +0.000002] amdgpu 0000:08:00.0: amdgpu: Fatal error during GPU init
[  +0.000008] amdgpu 0000:08:00.0: amdgpu: amdgpu: finishing device.
[  +0.000560] [drm] DSC precompute is not needed.
[  +0.000026] ------------[ cut here ]------------
[  +0.000001] WARNING: CPU: 10 PID: 2978 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:622 amdgpu_irq_put+0x46/0x70 [amdgp←
[  +0.000279] Modules linked in: ip_set nf_tables nfnetlink qrtr bnep nct6775 nct6775_core hwmon_vid sunrpc binfmt_misc←
[  +0.000028]  spi_nor iTCO_vendor_support snd_pcm drm_display_helper eeepc_wmi mei_hdcp mei_pxp intel_cstate asus_nb_w←
[  +0.000029] CPU: 10 PID: 2978 Comm: (udev-worker) Not tainted 6.7.4-200.fc39.x86_64 #1
[  +0.000003] Hardware name: ASUS System Product Name/PRIME Z690-P WIFI, BIOS 1620 08/12/2022
[  +0.000001] RIP: 0010:amdgpu_irq_put+0x46/0x70 [amdgpu]
[  +0.000185] Code: c0 74 33 48 8b 4e 10 48 83 39 00 74 29 89 d1 48 8d 04 88 8b 08 85 c9 74 11 f0 ff 08 74 07 31 c0 c3 ←
[  +0.000002] RSP: 0018:ffffbaa30152fb30 EFLAGS: 00010246
[  +0.000002] RAX: ffff9448568f5780 RBX: ffff944875298628 RCX: 0000000000000000
[  +0.000001] RDX: 0000000000000000 RSI: ffff9448752a43f8 RDI: ffff944875280000
[  +0.000001] RBP: ffff944875290178 R08: ffff944842005c80 R09: 000000008020001c
[  +0.000001] R10: ffff944847de5e00 R11: 0000000000000004 R12: ffff944875290558
[  +0.000001] R13: ffff944875280010 R14: ffff944875280000 R15: ffff9448752a43f8
[  +0.000001] FS:  00007f683a37c980(0000) GS:ffff944f9fa80000(0000) knlGS:0000000000000000
[  +0.000001] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  +0.000001] CR2: 000055ecc62e8188 CR3: 0000000153946000 CR4: 0000000000f50ef0
[  +0.000001] PKRU: 55555554
[  +0.000001] Call Trace:
[  +0.000002]  <TASK>
[  +0.000001]  ? amdgpu_irq_put+0x46/0x70 [amdgpu]
[  +0.000179]  ? __warn+0x81/0x130
[  +0.000004]  ? amdgpu_irq_put+0x46/0x70 [amdgpu]
[  +0.000179]  ? report_bug+0x171/0x1a0
[  +0.000003]  ? handle_bug+0x3c/0x80
[  +0.000003]  ? exc_invalid_op+0x17/0x70
[  +0.000001]  ? asm_exc_invalid_op+0x1a/0x20
[  +0.000003]  ? amdgpu_irq_put+0x46/0x70 [amdgpu]
[  +0.000179]  amdgpu_fence_driver_hw_fini+0xfe/0x130 [amdgpu]
[  +0.000183]  amdgpu_device_fini_hw+0xa6/0x3e0 [amdgpu]
[  +0.000155]  ? blocking_notifier_chain_unregister+0x36/0x50
[  +0.000004]  amdgpu_driver_load_kms+0xec/0x190 [amdgpu]
[  +0.000155]  amdgpu_pci_probe+0x165/0x4c0 [amdgpu]
[  +0.000152]  local_pci_probe+0x42/0xa0
[  +0.000004]  pci_device_probe+0xc7/0x240
[  +0.000002]  really_probe+0x19b/0x3e0
[  +0.000002]  ? __pfx___driver_attach+0x10/0x10
[  +0.000001]  __driver_probe_device+0x78/0x160
[  +0.000002]  driver_probe_device+0x1f/0x90
[  +0.000001]  __driver_attach+0xd2/0x1c0
[  +0.000002]  bus_for_each_dev+0x85/0xd0
[  +0.000003]  bus_add_driver+0x116/0x220
[  +0.000001]  driver_register+0x59/0x100
[  +0.000002]  ? __pfx_amdgpu_init+0x10/0x10 [amdgpu]
[  +0.000152]  do_one_initcall+0x58/0x320
[  +0.000004]  do_init_module+0x60/0x240
[  +0.000003]  __do_sys_init_module+0x17f/0x1b0
[  +0.000001]  ? __seccomp_filter+0x32c/0x4f0
[  +0.000004]  do_syscall_64+0x61/0xe0
[  +0.000002]  ? exc_page_fault+0x7f/0x180
[  +0.000002]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[  +0.000002] RIP: 0033:0x7f683ad3494e
[  +0.000019] Code: 48 8b 0d e5 14 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 ←
[  +0.000002] RSP: 002b:00007ffcc2a53b78 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[  +0.000002] RAX: ffffffffffffffda RBX: 00005596042b6c40 RCX: 00007f683ad3494e
[  +0.000001] RDX: 00007f683b24307d RSI: 00000000019b543e RDI: 00007f6836400010
[  +0.000001] RBP: 00007ffcc2a53c30 R08: 0000559603ad8010 R09: 0000000000000007
[  +0.000001] R10: 0000000000000002 R11: 0000000000000246 R12: 00007f683b24307d
[  +0.000001] R13: 0000000000020000 R14: 0000559603c509c0 R15: 00005596042baf90
[  +0.000001]  </TASK>
[  +0.000001] ---[ end trace 0000000000000000 ]---

I dual boot with Windows 11 and Windows 11 reboots work.

1 Like

I raised 2264573 – kernel panic in amdgpu after reboot with rx 7800 GPU for this bug.
The template for the bug asks to test with the rawhide kernel and that does work.
The kernel I tested was kernel-6.8.0-0.rc4.20240215git8d3dea210042.38.fc41.x86_64
To install that kernel I followed these steps:

dnf install fedora-repos-rawhide
dnf update --enablerepo=rawhide kernel

Then I powered down and did the reboot test and it worked.

1 Like

Sounds good! I only tested kernel 6.8.0-0.rc0.20240112git70d201a40823.5.fc40 in Rawhide-ISO “Fedora-KDE-Live-x86_64-Rawhide-20240125.n.0.iso” and got the issue.

Also using Windows 11 in dual boot and don’t have issues here.

Thanks! :+1:

I got 6.7.5-200.fc39.x86_64 today from updates-testing and can now reboot normally

1 Like

It looks like that the reboot issue is still there … :confused:

https://bodhi.fedoraproject.org/updates/FEDORA-2024-88847bc77a#comment-3414636