Cannot Wake from Suspend | F39 | kernel 6.7.6-200

Ask Fedora
, , , , , , , , ,
1

Welp, It’s my turn to not be able to wake from Suspend. . .

I put the laptop on Suspend from the menu, from the library to the Coffee shop 20mins later, lift lid, and Black screen. It appears the monito does not wake , the LED goes from blinking ( a suspend feature ) to on ( normal function ) Monitor does not come up.

Lenovo IdeapadGaming 3 | Fedora 39 Workstation |

uname -r
uname -r 6.7.6-200.fc39.x86_64

Gnome Logs is the only relevant info in the logs I could get.

5:05:42 PM gdm-session-wor: gkr-pam: the password for the login keyring was invalid.
  1  5:04:27 PM wpa_supplicant: bgscan simple: Failed to enable signal strength monitoring
  2  5:04:24 PM kernel: mt7921e 0000:03:00.0: PM: failed to resume async: error -110
  3  5:03:11 PM wpa_supplicant: bgscan simple: Failed to enable signal strength monitoring
  4  5:03:08 PM kernel: mt7921e 0000:03:00.0: PM: failed to resume async: error -110
  5  5:02:53 PM wpa_supplicant: bgscan simple: Failed to enable signal strength monitoring
  6  5:02:50 PM kernel: mt7921e 0000:03:00.0: PM: failed to resume async: error -110
  7  5:01:36 PM wpa_supplicant: bgscan simple: Failed to enable signal strength monitoring
  8  5:01:33 PM kernel: mt7921e 0000:03:00.0: PM: failed to resume async: error -110
  9  4:38:21 PM wpa_supplicant: bgscan simple: Failed to enable signal strength monitoring

inxi -Fxz Dump

System:
  Kernel: 6.7.6-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: GNOME v: 45.4 Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Laptop System: LENOVO product: 82K2 v: IdeaPad Gaming 3 15ACH6
    serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76465 WIN serial: <filter>
    UEFI: LENOVO v: H3CN32WW(V2.02) date: 02/23/2022
Battery:
  ID-1: BAT1 charge: 39.5 Wh (94.3%) condition: 41.9/45.0 Wh (93.0%)
    volts: 13.0 min: 11.5 model: 0x43 0x65 0x6C 0x78 0x70 0x72 0x74 0x00 0x32
    0x30 0x4C 0x32 0x30 0x43 0x33 0x50 status: charging
CPU:
  Info: 6-core model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 1088 high: 2628 min/max: 400/4280 cores: 1: 400 2: 2307
    3: 400 4: 2628 5: 1762 6: 400 7: 400 8: 400 9: 1572 10: 400 11: 1998 12: 400
    bogomips: 79050
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 bus-ID: 05:00.0
    temp: 37.0 C
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    bus-ID: 1-3:2
  Display: wayland server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~120Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 23.3.6 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
    17.0.6 DRM 3.57 6.7.6-200.fc39.x86_64)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 05:00.1
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    bus-ID: 05:00.5
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 05:00.6
  API: ALSA v: k6.7.6-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 2000 bus-ID: 02:00.0
  IF: enp2s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel bus-ID: 03:00.0
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai MediaTek Bluetooth Adapter driver: btusb v: 0.8
    type: USB bus-ID: 1-4:4
  Report: btmgmt ID: hci0 rfk-id: 8 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Sensors:
  System Temperatures: cpu: 53.1 C mobo: 36.0 C gpu: amdgpu temp: 36.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 28 GiB available: 27.25 GiB used: 4.46 GiB (16.4%)
  Processes: 389 Uptime: 2h 7m Init: systemd target: graphical (5)
  Packages: 97 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.26
    inxi: 3.3.33

I just upgraded to Fedora 39 yesterday, so i only have 2 Fedora 38 kernels left.

The results of journalctl | grep -iE 'error|warn|critical' provided no relevant info.

it’s kind of difficult to troubleshoot a problem that doesn’t report errors, I would definitely file a bug if I have relevant info. would have been even nicer if it came up in Gnome Problem Reporting so i could just forward it.

Here is bootctl list if anyone thinks it could be relevant

         type: Boot Loader Specification Type #1 (.conf)
        title: Fedora Linux 39 (Workstation Edition) (default) (selected)
           id: ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.6-200.fc39.x86_64.conf
       source: /boot/efi//loader/entries/ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.6-200.fc39.x86_64.conf
     sort-key: fedora
      version: 6.7.6-200.fc39.x86_64
   machine-id: ecc5b5e914994eb48de9d5fda2cd1ae6
        linux: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.6-200.fc39.x86_64/linux
       initrd: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.6-200.fc39.x86_64/initrd
      

         type: Boot Loader Specification Type #1 (.conf)
        title: Fedora Linux 38 (Workstation Edition) (6.7.6-100.fc38.x86_64)
           id: ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.6-100.fc38.x86_64.conf
       source: /boot/efi//loader/entries/ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.6-100.fc38.x86_64.conf
     sort-key: fedora
      version: 6.7.6-100.fc38.x86_64
   machine-id: ecc5b5e914994eb48de9d5fda2cd1ae6
        linux: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.6-100.fc38.x86_64/linux
       initrd: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.6-100.fc38.x86_64/initrd
     

         type: Boot Loader Specification Type #1 (.conf)
        title: Fedora Linux 38 (Workstation Edition) (6.7.5-100.fc38.x86_64)
           id: ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.5-100.fc38.x86_64.conf
       source: /boot/efi//loader/entries/ecc5b5e914994eb48de9d5fda2cd1ae6-6.7.5-100.fc38.x86_64.conf
     sort-key: fedora
      version: 6.7.5-100.fc38.x86_64
   machine-id: ecc5b5e914994eb48de9d5fda2cd1ae6
        linux: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.5-100.fc38.x86_64/linux
       initrd: /boot/efi//ecc5b5e914994eb48de9d5fda2cd1ae6/6.7.5-100.fc38.x86_64/initrd
      
         type: Automatic
        title: Reboot Into Firmware Interface
           id: auto-reboot-to-firmware-setup
       source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

Here is a screenshot from the Gnome Logs app with errors :

mt7921e 0000:03:00.0: PM: failed to resume async: error -110
mt7921e 0000:03:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110

Screenshot from 2024-03-01 17-14-48
Screenshot from 2024-03-01 17-14-481540×653 78.9 KB

Reproducible with same error in the logs :

mt7921e 0000:03:00.0: PM: failed to resume async: error -110
mt7921e 0000:03:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -110

2

After more testing, The screen will come on after about ~3min, It’s about right before the timeout for the screen to sleep again. I have tested this several times, I have filed a bug

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

This one was closed as unrelated to Gnome team :

3

Do you have checked if there is not a newer firmware for your Hardware?

4

I just upgraded to F39 2 days ago, and this was the first issue since then. Looking at my bootctl

Fedora Linux 39 (Workstation Edition) (6-6.7.6-200.fc39.x86_64)
Fedora Linux 38 (Workstation Edition) (6.7.6-100.fc38.x86_64)
Fedora Linux 38 (Workstation Edition) (6.7.5-100.fc38.x86_64)

I’m happy I did not remove the kernel pkgs and the grub/grubby packages like I typically do after an system-update. Reverting back to F38 6.7.6-100 is not a problem, neither is F38 6.7.5. I’m going to check for updates while I’m on wifi here, and check back. There was no update available earlier…


#### DNF Updates ####

Last metadata expiration check: 3:30:16 ago on Sat 02 Mar 2024 10:17:03 AM EST.
Dependencies resolved.
Nothing to do.
Complete!

#### Flatpak Updates  ####

Looking for updates…

Nothing to do.
5

Noticed same issue with my sons old Dell Laptop today.

System:
  Kernel: 6.7.4-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: MATE v: 1.26.2 wm: marco dm: 1: LightDM note: stopped 2: LXDM
    3: SDDM note: stopped 4: SLiM note: stopped Distro: Fedora Linux 39 (i3)
Machine:
  Type: Portable System: Dell product: Inspiron 3135 v: N/A
    serial: <superuser required> Chassis: type: 8 v: A02
    serial: <superuser required>
  Mobo: Dell model: 001GW6 v: A00 serial: <superuser required> part-nu: 0614
    UEFI: Dell v: A02 date: 01/03/2014
Battery:
  ID-1: BAT0 charge: 3.7 Wh (100.0%) condition: 3.7/4.5 Wh (82.4%) volts: 12.4
    min: 11.4 model: SDI Dell serial: <filter> status: full
CPU:
  Info: quad core model: AMD A6-1450 APU with Radeon HD Graphics bits: 64
    type: MCP arch: Jaguar rev: 1 cache: L1: 256 KiB L2: 2 MiB
  Speed (MHz): avg: 798 high: 799 min/max: 600/1000 boost: enabled cores:
    1: 799 2: 799 3: 798 4: 799 bogomips: 7985
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Temash [Radeon HD 8250/8280G] vendor: Dell driver: radeon
    v: kernel arch: GCN-2 ports: active: HDMI-A-1,LVDS-1 empty: none
    bus-ID: 00:01.0 chip-ID: 1002:983d
6

I still think this block is relevant, but I can’t figure it out at them moment. It’s kind of workflow breaking for me since I have to move place from time to time while working on things.

7

It looks like the WIFI chip is causing the issue. As several other distro’s have this issue listed it looks like a regression who is not in the newest kernel yet ?!

8

Im glad I reported it anyway, It wasn’t in the logs for me, and it’s a pretty big deal in my opinion. It took a while for me to wake from suspend. Has broken my workflow a bit since this happened since I move at least once a day to a new location.