Fedora won't wake up from suspended state

Ask Fedora
, , , , ,
1

I’ve been having issues with Fedora sometimes not waking up from sleep. I have to cut the power and boot it up again. Screen remains black and I can’t even switch to different tty.
Most of the time, it wakes up fine, but sometimes, it doesn’t.

I was concerned that nvidia might be the culprit, but even if I turn the card off in bios, it doesn’t seem to help.

This issue started ever since the 6.0 kernel came out. I’m using 5.15 LTS without any issues, but was hoping to move to 6.0 eventually, when they fix the issue, but it’s been quite a while and it’s still happening.

There seems to be nothing in the logs. But here’s the full log of the issue anyway.

May 27 00:34:20 aerie systemd-logind[1588]: The system will suspend now!
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5040] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 27 00:34:20 aerie ModemManager[1828]: <info>  [sleep-monitor-systemd] system is about to suspend
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5048] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5136] device (p2p-dev-wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5138] manager: NetworkManager state is now ASLEEP
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5139] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 27 00:34:20 aerie systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
May 27 00:34:20 aerie audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
May 27 00:34:20 aerie systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
May 27 00:34:20 aerie kernel: wlp3s0: deauthenticating from 52:42:89:7e:b4:2c by local choice (Reason: 3=DEAUTH_LEAVING)
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=52:42:89:7e:b4:2c reason=3 locally_generated=1
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5705] device (wlp3s0): supplicant interface state: completed -> disconnected
May 27 00:34:20 aerie avahi-daemon[1542]: Withdrawing address record for fd00::6f05:3a7d:df98:b863 on wlp3s0.
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5707] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5746] dhcp4 (wlp3s0): canceled DHCP transaction
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5746] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 27 00:34:20 aerie avahi-daemon[1542]: Withdrawing address record for 2a01:4b00:f03e:7e00:a038:1d55:7231:f6d1 on wlp3s0.
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5746] dhcp4 (wlp3s0): state changed no lease
May 27 00:34:20 aerie avahi-daemon[1542]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address 2a01:4b00:f03e:7e00:a038:1d55:7231:f6d1.
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5748] dhcp6 (wlp3s0): canceled DHCP transaction
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5748] dhcp6 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5748] dhcp6 (wlp3s0): state changed no lease
May 27 00:34:20 aerie avahi-daemon[1542]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::8fc2:1129:14d1:51e7.
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.5874] device (wlp3s0): set-hw-addr: set MAC address to 9E:03:86:96:B7:59 (scanning)
May 27 00:34:20 aerie avahi-daemon[1542]: Registering new address record for fe80::8fc2:1129:14d1:51e7 on wlp3s0.*.
May 27 00:34:20 aerie avahi-daemon[1542]: Withdrawing address record for fe80::8fc2:1129:14d1:51e7 on wlp3s0.
May 27 00:34:20 aerie avahi-daemon[1542]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::8fc2:1129:14d1:51e7.
May 27 00:34:20 aerie avahi-daemon[1542]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
May 27 00:34:20 aerie avahi-daemon[1542]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
May 27 00:34:20 aerie avahi-daemon[1542]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.206.
May 27 00:34:20 aerie avahi-daemon[1542]: Withdrawing address record for 192.168.1.206 on wlp3s0.
May 27 00:34:20 aerie avahi-daemon[1542]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.206.
May 27 00:34:20 aerie avahi-daemon[1542]: New relevant interface wlp3s0.IPv4 for mDNS.
May 27 00:34:20 aerie avahi-daemon[1542]: Registering new address record for 192.168.1.206 on wlp3s0.IPv4.
May 27 00:34:20 aerie avahi-daemon[1542]: Withdrawing address record for 192.168.1.206 on wlp3s0.
May 27 00:34:20 aerie avahi-daemon[1542]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.206.
May 27 00:34:20 aerie avahi-daemon[1542]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
May 27 00:34:20 aerie systemd-resolved[1501]: wlp3s0: Bus client reset search domain list.
May 27 00:34:20 aerie dnsmasq[2068]: reading /etc/resolv.conf
May 27 00:34:20 aerie systemd-resolved[1501]: wlp3s0: Bus client set default route setting: no
May 27 00:34:20 aerie dnsmasq[2068]: using nameserver 127.0.0.53#53
May 27 00:34:20 aerie systemd-resolved[1501]: wlp3s0: Bus client reset DNS server list.
May 27 00:34:20 aerie audit[1833]: NETFILTER_CFG table=firewalld:14 family=1 entries=41 op=nft_unregister_rule pid=1833 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.6141] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 27 00:34:20 aerie NetworkManager[1860]: <info>  [1716766460.6266] device (wlp3s0): set-hw-addr: reset MAC address to 98:22:EF:D7:17:8D (unmanage)
May 27 00:34:20 aerie chronyd[1830]: Source 80.82.244.120 offline
May 27 00:34:20 aerie chronyd[1830]: Source 80.87.128.222 offline
May 27 00:34:20 aerie chronyd[1830]: Source 162.159.200.123 offline
May 27 00:34:20 aerie chronyd[1830]: Can't synchronise: no selectable sources
May 27 00:34:20 aerie chronyd[1830]: Source 85.199.214.98 offline
May 27 00:34:20 aerie systemd[1]: Reached target sleep.target - Sleep.
May 27 00:34:20 aerie wpa_supplicant[1918]: p2p-dev-wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
May 27 00:34:20 aerie wpa_supplicant[1918]: p2p-dev-wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
May 27 00:34:20 aerie wpa_supplicant[1918]: nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
May 27 00:34:20 aerie systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
May 27 00:34:20 aerie suspend[65334]: nvidia-suspend.service
May 27 00:34:20 aerie logger[65334]: <13>May 27 00:34:20 suspend: nvidia-suspend.service
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
May 27 00:34:20 aerie wpa_supplicant[1918]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
May 27 00:34:20 aerie wpa_supplicant[1918]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "41"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event2  - Power Button: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "44"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event8  - Video Bus: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "45"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event7  - Video Bus: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "46"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event1  - Power Button: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "47"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "48"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "52"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event12 - Ideapad extra buttons: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "53"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event3  - AT Translated Set 2 keyboard: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "54"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event11 - SynPS/2 Synaptics TouchPad: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "47"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event5  - Logitech Wireless Keyboard PID:4023: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (**) Option "fd" "48"
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) event6  - Logitech Wireless Mouse: device removed
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) AIGLX: Suspending AIGLX clients for VT switch
May 27 00:34:21 aerie kernel: rfkill: input handler enabled
May 27 00:34:21 aerie gsd-media-keys[3550]: Unable to get default source
May 27 00:34:21 aerie gsd-media-keys[3550]: Unable to get default sink
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/ldac
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/aac
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aac
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc_xq
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc_xq
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/faststream
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/opus_05
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/opus_05
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 27 00:34:21 aerie bluetoothd[1544]: Endpoint unregistered: sender=:1.81 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 27 00:34:21 aerie uresourced[2122]: Setting resources on user-1000.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
May 27 00:34:21 aerie uresourced[2122]: Setting resources on user@1000.service (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
May 27 00:34:21 aerie uresourced[2122]: Setting resources on user.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: -, IOWeight: -)
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:65
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:69
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:66
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:75
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:71
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:67
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:72
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:70
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 13:76
May 27 00:34:21 aerie /usr/libexec/gdm-x-session[2965]: (II) systemd-logind: got pause for 226:0
May 27 00:34:21 aerie systemd[1]: nvidia-suspend.service: Deactivated successfully.
May 27 00:34:21 aerie systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
May 27 00:34:21 aerie audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
May 27 00:34:21 aerie audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? >
May 27 00:34:21 aerie systemd[1]: Starting systemd-suspend.service - System Suspend...
May 27 00:34:21 aerie systemd-sleep[65368]: Entering sleep state 'suspend'...
-- Boot a911b662b3aa4f61a4427124e8b4b8a3 --
May 27 05:23:32 aerie kernel: Linux version 6.8.10-200.fc39.x86_64 (mockbuild@f9cdabb4fa2740de85a9acfb428ce3fd) (gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7), GNU ld version 2.40-14.fc39) #1 SMP PREEMPT_DYNAMIC>

As you can see, there’s nothing in the logs about me trying to wake the system up. The next message is the new boot from after I forced shutdown.

I’m not sure how should I investigate this further, but I’m hoping I’m not the only with this issue.

2

Removed server

3

Could you post your system specs here using inxi -Fxzz in </> preformatted text?

There have been many issues with Wake from Suspend here in the last few months with different 6.7.+ kernels. I am currently on 6.8.11 and do not have issues.

Also, if you know your 5.15 LTS kernel is good, then keep it and use it as a fall back.

4

This reminds me of black screen issues that sre back for me it is sonething to do with power managment prob since i have been having this daily on my laptopbwuthbexternal screen and it wont show anything on both screens untill ibdisconnect external monitor and then i get laptop screen back and log in connect external screen bqck and all wirks again. Could this be similar onnyour case too?

5

I was having a similar problem a few weeks back. It eventually went away after I updated, but I never was able to pinpoint what was causing it.

6 
System:
  Kernel: 5.15.160-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Console: pty pts/2 Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Laptop System: LENOVO product: 80WK v: Lenovo Y520-15IKBN
    serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <filter> UEFI: LENOVO
    v: 4KCN40WW date: 10/17/2017
Battery:
  ID-1: BAT0 charge: 31.0 Wh (100.0%) condition: 31.0/45.0 Wh (68.9%)
    volts: 12.7 min: 11.5 model: SMP L16M3P24 status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i5-7300HQ bits: 64 type: MCP
    arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2289 high: 3289 min/max: 800/3500 cores: 1: 1128 2: 3149
    3: 3289 4: 1592 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: Lenovo
    driver: nvidia v: 550.90.07 arch: Pascal bus-ID: 01:00.0
  Device-3: Syntek EasyCamera driver: uvcvideo type: USB bus-ID: 1-6:3
  Display: server: X.Org v: 1.20.14 with: Xwayland v: 23.2.7 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 1: 1920x1200~60Hz 2: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.6 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel CM238 HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3
  API: ALSA v: k5.15.160-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: n/a (root, process)
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Lenovo driver: ath10k_pci v: kernel bus-ID: 03:00.0 temp: 47.0 C
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 3000 bus-ID: 04:00.0
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-2: virbr1 state: up speed: 10 Mbps duplex: unknown mac: <filter>
  IF-ID-3: vnet0 state: unknown speed: 10 Mbps duplex: full mac: <filter>
  IF-ID-4: vnet1 state: unknown speed: 10 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 driver: btusb v: 0.8
    type: USB bus-ID: 1-11:4
  Report: btmgmt ID: hci0 rfk-id: 5 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 1.94 TiB lvm-free: 180 GiB used: 1.44 TiB (74.6%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW128HEGR-000L2
    size: 119.24 GiB temp: 35.9 C
  ID-2: /dev/sda vendor: Seagate model: ST2000LM007-1R8174 size: 1.82 TiB
    temp: 39 C
Partition:
  ID-1: / size: 118.13 GiB used: 99.19 GiB (84.0%) fs: btrfs dev: /dev/dm-0
    mapped: luks-b9a4d92b-a9b0-4931-97d5-a9d03127396c
  ID-2: /boot size: 973.4 MiB used: 577.3 MiB (59.3%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 99.8 MiB used: 19 MiB (19.0%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 118.13 GiB used: 99.19 GiB (84.0%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-b9a4d92b-a9b0-4931-97d5-a9d03127396c
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.57 GiB (19.6%) dev: /dev/zram0
  ID-2: swap-2 type: partition size: 20 GiB used: 0 KiB (0.0%)
    dev: /dev/dm-4 mapped: hdd-swap
Sensors:
  System Temperatures: cpu: 42.0 C pch: 43.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.5 GiB used: 7.68 GiB (49.6%)
    igpu: 32 MiB
  Processes: 445 Uptime: 21h 22m Init: systemd target: graphical (5)
  Packages: 89 Compilers: gcc: 13.3.1 Shell: Sudo v: 1.9.15p5 inxi: 3.3.34
7

My issues were with 6.8.10 if I remember correctly.

8

If it was only few weeks back, give it time. I thought it was sorted a couple times, until it happened again. It seems to be random and there can be breaks when it doesn’t happen for a while (and also times where it happens fairly often).

9

Good practice would be to keep a couple kernels in when you know you have a good one. Depending on your bootlloader you can change that and since you are suing a LTS you probably should.

Wake/Suspend will be different for everyone, Power/Wifi/Bluetooth are all affected at times as well.

10

So it looks like the problem isn’t with waking up, it’s with putting it to sleep.
For some reason, the process doesn’t finish and the device gets stuck in powered up mode.

I wasn’t able to spot any difference in the systemd journal logs between a successful sleep and unsuccessful one. Both end with that “entering sleep state ‘suspend’” message as is shown in the original post.

It looks like the latest 5.15 LTS kernels have the same problem as the current fedora kernel, so there’s no longer any benefit in using the LTS version.

I wonder if there are any other logs, outside the systemd journal or anything else I should check.

Given that changing the kernel version seemed to have helped before, I think it’s more likely to be software issue than a hardware issue.

PS: couple times I got a seemingly similar problem when powering down… it would go through all the steps but wouldn’t actually power down, due to the fact that I don’t usually shutdown (mostly just reboot, which seems to work fine), I’m not yet sure if this is in fact related or if it happens with about the same frequency, nor if it does actually get stuck there permanently or if it simply takes too long.