Hi, this is a cross-post from the Fedora discussion page as I haven’t had any response at all and (as below) I have had a kernel update and the issue persists, so I am wondering if it’s possibly a KDE issue.
I’m running Fedora 42 on a HP Pavilion with kernel 6.14.11-300.fc42.x86_64, with KDE6.4 (it happens on 6.3 as well)
When my laptop goes into suspend it will hard freeze when coming back out. I have run an ssh session from another machine to watch dmesg as it goes down but upon “waking” the session doesn’t come back, it’s not just graphically frozen. I can’t get into another tty.
I have also tried enabling kdump and the output of kdumpctl status is
sudo kdumpctl status
kdump: Kdump is operational
kdump: Notice: Last successful vmcore creation on Thu 19 Jun 11:27:09 BST 2025
The vmcore that is created is just one from kdumpctl test. I am unable to get a crash dump from when I suspend/resume to even start to have a look at it.
Please can someone help as to what else I can try to see where the issue might be. I am not sure exactly when it started unfortunately as I don’t use my laptop all that much, so I couldn’t say on kernel X.xx it was fine for example.
Kernel has updated to Linux 6.15.3-200.fc42.x86_64 and the problem persists.
what are the contents of the [Sleep] section of /etc/systemd/sleep.conf?
what are the outputs of
cat /sys/power/state
cat /sys/power/mem_sleep
cat /sys/power/disk
what does swapon say?
Hi, thanks for the reply, here are all the outputs:
root@breemer-laptop:~# cat /etc/systemd/sleep.conf
cat: /etc/systemd/sleep.conf: No such file or directory
root@breemer-laptop:~# cat /sys/power/state
freeze mem disk
root@breemer-laptop:~# cat /sys/power/mem_sleep
[s2idle]
root@breemer-laptop:~# cat /sys/power/disk
[platform] shutdown reboot suspend test_resume
root@breemer-laptop:~# swapon
NAME TYPE SIZE USED PRIO
/dev/zram0 partition 8G 0B 100
root@breemer-laptop:~#
does fedora not have a systemd directory, or do you just not have that file?
if the directory is there, but there is no file you can create one (as root).
they generally look like this:
[Sleep]
# AllowSuspend=yes
# AllowHibernation=yes
# AllowSuspendThenHibernate=yes
# AllowHybridSleep=yes
# SuspendState=mem standby freeze
# HibernateMode=platform shutdown
# MemorySleepMode=
# HibernateDelaySec=
# SuspendEstimationSec=60min
do you have secure boot enabled in the bios?
also, i would not use zram for swap, and try just a file instead or better yet a regular partition, but swap is mainly if you want to hibernate (S4 save to disk) in addition to sleep (S3 save to RAM).
Fedora does have /etc/systemd but that file only existed in /usr/lib/systemd. I’ve copied it over to /etc just in case as well. It seems zram is used because Fedora uses btrfs by default, I have managed to switch it over to a normal swap file, but the problem persists. Secure boot is disabled
i’m afraid we reaching the limits of my knowledge on this as i’m only (passingly) familiar with how systemd works on kubutnu and have no idea what fedora is doing.
if that file exists in /usr/lib/systemd on fedora then i would suggest working with that file rather than copying it somewhere else.
you can try making the following edits to ensure it’s not trying to hibernate and just limit suspend operations to the s2idle state.
[Sleep]
# AllowSuspend=yes
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
# SuspendState=mem standby freeze
# HibernateMode=platform shutdown
# MemorySleepMode=
# HibernateDelaySec=
# SuspendEstimationSec=60min
you can also look at
cat /proc/acpi/wakeup
to get an idea what acpi calls are supported by your hardware… mine shows nothing for S3, yet S3 still works.
the fact that my cat /sys/power/mem_sleep shows
s2idle [deep]
means that S3 is fully supported and that [deep] is the default option.
perhaps there is a bios setting for suspend to RAM that you can enable…
root@breemer-laptop:~# cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP1 S4 *disabled
GPP2 S4 *enabled pci:0000:00:01.3
GP17 S4 *enabled pci:0000:00:08.1
GPP0 S4 *disabled
root@breemer-laptop:~# cat /sys/power/mem_sleep
[s2idle]
root@breemer-laptop:~#
These are the outputs of those files. I will have a look in the BIOS just in case but I haven’t changed anything there and it definitely used to work
I’m going to do some more testing, but I think I have found the answer. It might be my automounts to my remote NAS through tailscale. I have disabled those and so far it looks like my laptop is waking correctly. I’m pretty sure it used to work in the past but it’s not so important I can’t live without them and can manually mount when necessary. I really appreciate the replies and help
for me cat /proc/acpi/wakeup give me a platform acpi call like this
AWAC S4 *enabled platform:ACPI000E:00
and when i do cat /sys/power/disk i get
[platform] shutdown reboot suspend test_resume
showing [platform] as the current setting, meaning it hands over control to the firmware for waking back up again… but your system doesn’t seem to offer that option, so it won’t wake from hibernation.
it should still wake from sleep tho, which, in your case is only S2 with minimal power savings.. you might look in your bios for energy savings or ERP mode .
this is another reason why i suggest deliberately deactivating any attempt to hibernate (S4 write RAM to disk) and just rely on sleep mode (freeze in your case).
both motherboards i tried had issues with freeze (s2idle) so i ended up relying on mem and deep to save the system state in RAM for the sleep portion of my suspend operation… only later (after 3hrs) does it wake up and then enter into hibernate (S4 by writing the system state to disk).
Really appreciate the help, Skyfishgoo. Things seem to be okay since disabling those mounts so I’m hoping it was that in the end.
1 Like