Laptop cannot wake up from sleep on fedora 37

As soon as my laptop is suspended it cannot wake up, I cannot turn it on unless I reboot it. Is anyone having a similar issue? I would appreciate it if you could help to fix it

1 Like

Does it work on an older kernel?
Can you post the laptop information or inxi -Fz
you will probably want to start by looking at the logs, Viewing logs in Fedora :: Fedora Docs

thanks

3 Likes

I mean it has not even been a week since I moved from ubuntu to fedora. So I do not have any older kernel

Here it is :

System:
  Kernel: 6.1.9-200.fc37.x86_64 arch: x86_64 bits: 64 Desktop: GNOME v: 43.2
    Distro: Fedora release 37 (Thirty Seven)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA506IH_FA506IH
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FA506IH v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: FA506IH.316 date: 03/12/2021
Battery:
  ID-1: BAT1 charge: 10.4 Wh (31.9%) condition: 32.6/48.2 Wh (67.7%)
    volts: 10.8 min: 11.9
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1399 min/max: 1400/2900 cores: 1: 1400 2: 1400 3: 1400
    4: 1400 5: 1400 6: 1400 7: 1400 8: 1397 9: 1400 10: 1400 11: 1397 12: 1400
    13: 1400 14: 1397 15: 1397 16: 1400
Graphics:
  Device-1: NVIDIA TU117M driver: nvidia v: 525.85.05
  Device-2: AMD Renoir driver: amdgpu v: kernel
  Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
  Display: wayland server: X.Org v: 22.1.7 with: Xwayland v: 22.1.7
    compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.4 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.49 6.1.9-200.fc37.x86_64)
Audio:
  Device-1: NVIDIA driver: snd_hda_intel
  Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
  Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
  Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  Sound API: ALSA v: k6.1.9-200.fc37.x86_64 running: yes
  Sound Server-1: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    driver: rtw_8822ce
  IF: wlp3s0 state: down mac: <filter>
  Device-3: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB
    driver: r8188eu
  IF: wlp5s0f3u2 state: down mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
  Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 29.83 GiB (6.3%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: OM8PCP3512F-AB size: 476.94 GiB
Partition:
  ID-1: / size: 475.35 GiB used: 29.5 GiB (6.2%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 320.5 MiB (32.9%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.35 GiB used: 29.5 GiB (6.2%) 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.5 C mobo: N/A gpu: amdgpu temp: 39.0 C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 749 Uptime: 42m Memory: 15.05 GiB used: 4.55 GiB (30.3%)
  Shell: Bash inxi: 3.3.24

Thanks for your attention. Would really appreciate it if you could help me further!

Actually you may have an older kernel depending on how you did the install and if you have done an upgrade since.

  1. How did you install fedora 37? From the live ISO image or from the netinst ISO?
  2. Did you do the update immediately after the install?

If you installed using the netinst image then it automatically does a full update during the install and there would likely be no older kernel to boot.

If you installed from a live workstation image then it would have installed the 6.0.7 kernel and the upgrade would have installed either 6.1.8 or 6.1.9 depending on when you did the install & upgrade. In that case you should have at least one older kernel to test.

Please post the output screenfetch as well.

1 Like
Feb 01 23:44:39 fedora dbus-broker-launch[1875]: avc:  op=load_policy lsm=selinux seqno=3 res=1
Feb 01 23:44:43 fedora dbus-broker-launch[1875]: avc:  op=load_policy lsm=selinux seqno=4 res=1
Feb 01 23:44:50 fedora systemd[1833]: selinux: avc:  op=load_policy lsm=selinux seqno=4 res=1
Feb 01 23:44:55 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:55 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:55 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:56 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:44:58 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:02 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:04 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:10 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:10 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:10 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:11 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:11 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:11 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Noticed file-system modification, trigger reload.
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Feb 01 23:45:12 fedora dbus-broker-launch[1872]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored

The problem is that I do not really get what these messages mean and how to really work with them.

Here it is:

        :-------------------::        OS: Fedora 
      :-----------/shhOHbmp---:\      Kernel: x86_64 Linux 6.1.9-200.fc37.x86_64
    /-----------omMMMNNNMMD  ---:     Uptime: 52m
   :-----------sMMMMNMNMP.    ---:    Packages: 2030
  :-----------:MMMdP-------    ---\   Shell: pkcommand-not-found
 ,------------:MMMd--------    ---:   Resolution: 1920x1080
 :------------:MMMd-------    .---:   DE: GNOME 43.2
 :----    oNMMMMMMMMMNho     .----:   WM: Mutter
 :--     .+shhhMMMmhhy++   .------/   WM Theme: Adwaita
 :-    -------:MMMd--------------:    GTK Theme: Adwaita [GTK2/3]
 :-   --------/MMMd-------------;     Icon Theme: Adwaita
 :-    ------/hMMMy------------:      Font: Cantarell 11
 :-- :dMNdhhdNMMNo------------;       Disk: 60G / 953G (7%)
 :---:sdNMMMMNds:------------:        CPU: AMD Ryzen 7 4800H with Radeon Graphics @ 16x 2.9GHz
 :------:://:-------------::          GPU: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.9-200.fc37.x86_64)
 :---------------------://            RAM: 4689MiB / 15408MiB

I have two same kernels to boot! Both of them are what I have posted. I installed it through ISO with Media writer. But I do not have that 6.0.7

I believe there was an update to the selinux policy in the last couple days.

I received this on my daily update on Sunday 5 February.

Upgrade  selinux-policy-37.19-1.fc37.noarch                        @updates

and kernel 6.1.9 was installed on Saturday 4 February.

The log snippet you posted was all from February 1. Are you still getting those errors even with the newest kernel and a reboot either on Friday or later?

I was occasionally getting those same errors on February 3 but they have since stopped with my updates done just after midnight on Feb 4 (the same time kernel 6.1.9 was installed for me).
I see this in the logs for the time when my newest kernel was installed, related to dbus.

$ journalctl -b 0 | grep dracut | grep dbus
Feb 04 02:19:46 eagle.home.domain dracut[1050493]: *** Including module: dbus-broker ***
Feb 04 02:19:46 eagle.home.domain dracut[1050493]: *** Including module: dbus ***
Feb 04 02:19:54 eagle.home.domain dracut[1050493]: dbus-broker
Feb 04 02:19:54 eagle.home.domain dracut[1050493]: dbus
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   7 root     root            0 Nov 16 12:00 etc/dbus-1
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 etc/dbus-1/interfaces
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 etc/dbus-1/services
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          838 Oct  6 13:37 etc/dbus-1/session.conf
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 etc/dbus-1/session.d
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 etc/dbus-1/system-services
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          833 Oct  6 13:37 etc/dbus-1/system.conf
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 etc/dbus-1/system.d
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          409 Jan  9  2020 etc/dbus-1/system.d/teamd.conf
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: lrwxrwxrwx   1 root     root           43 Nov 16 12:00 etc/systemd/system/dbus.service -> /usr/lib/systemd/system/dbus-broker.service
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: -rwxr-xr-x   1 root     root       245808 Aug  5  2022 usr/bin/dbus-broker
Feb 04 02:19:55 eagle.home.domain dracut[1050493]: -rwxr-xr-x   1 root     root       133168 Aug  5  2022 usr/bin/dbus-broker-launch
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root         4246 Aug  5  2022 usr/lib/systemd/catalog/dbus-broker-launch.catalog
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root         2355 Aug  5  2022 usr/lib/systemd/catalog/dbus-broker.catalog
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          547 Aug  5  2022 usr/lib/systemd/system/dbus-broker.service
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          242 Nov 16 12:00 usr/lib/systemd/system/dbus.socket
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/lib/systemd/system/dbus.target.wants
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          469 Aug  5  2022 usr/lib/systemd/user/dbus-broker.service
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          213 Oct  6 13:34 usr/lib/systemd/user/dbus.socket
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          118 Oct  6 13:34 usr/lib/sysusers.d/dbus.conf
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: lrwxrwxrwx   1 root     root           31 Nov 16 12:00 usr/lib64/libdbus-1.so -> ../../lib64/libdbus-1.so.3.32.1
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: lrwxrwxrwx   1 root     root           31 Nov 16 12:00 usr/lib64/libdbus-1.so.3 -> ../../lib64/libdbus-1.so.3.32.1
Feb 04 02:19:58 eagle.home.domain dracut[1050493]: -rwxr-xr-x   1 root     root       353384 Oct  6 13:38 usr/lib64/libdbus-1.so.3.32.1
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   7 root     root            0 Nov 16 12:00 usr/share/dbus-1
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/share/dbus-1/interfaces
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/share/dbus-1/services
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root         3561 Oct  6 13:37 usr/share/dbus-1/session.conf
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/share/dbus-1/session.d
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/share/dbus-1/system-services
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root          412 Nov 16 12:00 usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root         5804 Oct  6 13:37 usr/share/dbus-1/system.conf
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: drwxr-xr-x   2 root     root            0 Nov 16 12:00 usr/share/dbus-1/system.d
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root         8150 Oct 10 08:58 usr/share/dbus-1/system.d/org.freedesktop.NetworkManager.conf
Feb 04 02:19:59 eagle.home.domain dracut[1050493]: -rw-r--r--   1 root     root        19779 Nov 16 12:00 usr/share/dbus-1/system.d/org.freedesktop.systemd1.conf

After that time I have no entries in my logs that are similar to those you posted.

1 Like

I mean, I still cannot wake it up from sleep.

Do you have any suggestions?

I don’t even know how to work with these messages.

Look in the logs using a command similar to the one I showed and see what it says.
Those messages should not be related to the failure to wake from sleep.
The log snippet I showed is related to the update of dbus modules and related when the kernel was updated, which by the timing and error messages seems to be the fix that stopped the dbus-broker-launch messages I was receiving

When you say sleep are you referring to the locked screen or suspension or hibernation or ??

1 Like

Interestingly enough, I have the exact same processor in my laptop and had the same thing happen to me yesterday. It appears to be a Ryzen/AMD GPU regression with this kernel. Seems to be specific to the 4800H, too. It’s not an issue on my 4750U.

2 Likes

In amd ryzen 4000 and 5000 the sleep issue very common even on windows i find this with ubuntu before and recently it is slightly more stable else before that i hace also find many instance which lead to the same issue if you sleep your system system never wake up.
I think it need to be a bug report in bugzilla about that issue.

locked screen and suspension both

on ubuntu I did not have this issue

I did not have this issue on ubuntu

good to know but it is your luck that you have not faced but while i was on kubuntu 22.10 i hope i find that issue and have not been solved for next 3 kernel release. so i have switched to fedora it was good but again i find the same issue in fedora after some research i find that it is actually a issue very common in that series 4000 5000 of laptops. also one of my friend have a system with 5700 cpu and he also have that same issue on windows.in my case in fedora after i posted a bug-report at redhat that fix was pushed on 2nd kernel update and fixed after that i never find that issue again.

1 Like

I would also like to report but how can I do that?

You can file a bug report at https://bugzilla.redhat.com

1 Like