Screen doesn't come back from suspension with Kernel 6.11.x

Hi there,

I’ve using Fedora 40 without any problems, almost for five months, until I upgraded to the 6.11.x Kernel version. If I use this Kernel, my screen won’t come back from suspension (the computer does come back), and sometimes I get some strange horizontal artifacts on screen, similar to an interference. If I turn the screen off/on, it goes away, but returns after a while.

If I use the 6.10.12, everything works great, so I’ll stay in this Kernel until this issue gets fixed.

Here go my specs:
MotherASRock X670E Steel Legend + AMD Ryzen 7 7700X + Corsair 64GB (2x32GB) 6200MHz CL32 Vengeance + Corsair RMx Shift 850W Plus Gold + Sapphire PULSE RX 7800 XT 16GB+Monitor Gigabyte M28U at 144Hz

José

3 Likes
1 Like

I face the same problem with kernel 6.11,
I have AMD Ryzen 7600 CPU
and AMD RX 7800XT GPU.
I tried Fedora 41 and it is the same.

1 Like

Added f40, kernel, suspend-resume

Indeed, I’m having this same issue, and it only started after the update to 6.11.x kernel.

Specs:
AMD Ryzen 5 5600
AMD Radeon RX 7600
Gigabyte B550M Motherboard
64GB G.Skill DDR4 2133 RAM
Fedora 41
KDE Plasma 6.2.2
Kernel 6.11.5-300

Did anyone try the 6.11.5 kernel to see if this issue is still present?

UPDATE: Oh, I’ve just realized that John mentioned this exactly Kernel version in his last post, so it doesn’t work, so I won’t upgrade to Fedora 41 just yet.

I have the same issue on both Fedora 40 and 41, I’m currently on v6.11.5-300.

Specs:

OS: Fedora Linux 41 (Workstation Edition) x86_64
Kernel: v6.11.5-300
Hardware model: Micro-Star International Co., Ltd. MS-7D77
CPU: AMD Ryzen™ 7 7700X × 16
GPU 1: AMD Radeon RX 6600 (Discrete)
GPU 2: AMD Raphael (Integrated)
RAM: 32.0GB

Last time this happened, it was due to a regression in the Mesa drivers for people with AMD GPUs, but it keeps occurring every few months.

I have the same issue on Fedora 41

I’ve read in another topic here in the forum that it might be Bluetooth related.

And that indeed seems to be my case. If I disable Bluetooth and then suspend the system, it wakes back just fine. But once I enable Bluetooth again, it doesn’t. Does disabling Bluetooth work for you?

Best

José

3 Likes

Yeah, once I disabled Bluetooth, I was able to suspend and wake my computer up. I don’t know if the kernel maintainers are aware of that, but it might be worth reporting it

Same issue! Turning off Bluetooth solved the issue as well.

Not sure if it’s relevant, but here is my info:

kitty@fedora:~$ fastfetch --logo none
kitty@fedora
------------
OS: Fedora Linux 41 (Workstation Edition) x86_64
Host: 82R4 (IdeaPad 1 15ALC7)
Kernel: Linux 6.11.5-300.fc41.x86_64
Uptime: 52 mins
Packages: 2415 (rpm), 41 (flatpak)
Shell: bash 5.2.32
Display (AUO61ED): 1920x1080 @ 60 Hz in 15" [Built-in]
DE: GNOME 47.1
WM: Mutter (Wayland)
WM Theme: Adwaita
Theme: Adwaita [GTK2/3/4]
Icons: Adwaita [GTK2/3/4]
Font: Cantarell (11pt) [GTK2/3/4]
Cursor: Adwaita (24px)
Terminal: GNOME Terminal 3.54.0
Terminal Font: Source Code Pro (10pt)
CPU: AMD Ryzen 5 5500U (12) @ 4.06 GHz
GPU: AMD Lucienne [Integrated]
Memory: 3.00 GiB / 5.62 GiB (53%)
Swap: 40.77 MiB / 5.62 GiB (1%)
Disk (/): 22.87 GiB / 475.35 GiB (5%) - btrfs
Local IP (wlp2s0): 192.168.50.133/24
Battery (L21L3PF0): 87% [Discharging]
Locale: en_US.UTF-8

I was looking around to see if other distros were seeing this issue and found it reported on Arch too. I wanted to see if anyone was working on fixing this. The Arch post linked to this kernel bug report. Looks like it’s being discussed, but no fix yet:

https://bugzilla.kernel.org/show_bug.cgi?id=219290

3 Likes

Dupe of Kernel 6.11.3-200.fc40 unable to resume from suspend when bluetooth enabled.

I posted a script there that may provide a workaround (haven’t tested it on Fedora workstation but worked on Tumbleweed).

2 Likes