laptop does not go to suspend

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Post Reply
zlinqi
Level 1
Level 1
Posts: 5
Joined: Tue Jan 23, 2024 4:06 am

laptop does not go to suspend

Post by zlinqi »

Dear experts,

My new laptop does not go into suspend state. Any idea how to fix it? Thanks.

Here is the relevant info - let me know if any other info is needed:

log info in /var/log/syslog when I trigger the suspend request from menu:

Code: Select all

Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.0917] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 23 16:09:06 Qihe ModemManager[959]: <info>  [sleep-monitor-systemd] system is about to suspend
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.0918] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 16:09:06 Qihe dbus-daemon[844]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=847 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.0919] device (44:71:47:2F:D1:68): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.0921] manager: NetworkManager state is now ASLEEP
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.0921] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 16:09:06 Qihe systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 23 16:09:06 Qihe dbus-daemon[844]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 23 16:09:06 Qihe systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 23 16:09:06 Qihe kernel: [23301.527923] wlp1s0: deauthenticating from 7c:de:78:4d:b8:a1 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=7c:de:78:4d:b8:a1 reason=3 locally_generated=1
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5477] device (wlp1s0): supplicant interface state: completed -> disconnected
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5479] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 16:09:06 Qihe avahi-daemon[837]: Withdrawing address record for fe80::f83c:ddcb:334e:9be5 on wlp1s0.
Jan 23 16:09:06 Qihe avahi-daemon[837]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::f83c:ddcb:334e:9be5.
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5483] dhcp4 (wlp1s0): canceled DHCP transaction
Jan 23 16:09:06 Qihe avahi-daemon[837]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5483] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5483] dhcp4 (wlp1s0): state changed no lease
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5485] dhcp6 (wlp1s0): canceled DHCP transaction
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:b8:a1 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4f:39:41 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:b8:a9 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:70:69 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:8f:e1 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4e:a5:61 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4e:a5:69 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 00:dd:b6:b1:ed:c1 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:8f:e9 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 58:b3:8f:99:f7:81 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4f:39:49 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:7d:69 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 00:dd:b6:b2:69:21 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:46:de:21 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 00:dd:b6:b1:eb:f1 0
Jan 23 16:09:06 Qihe systemd-resolved[825]: wlp1s0: Bus client set default route setting: no
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 00:dd:b6:b1:ed:d1 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:4d:81:09 0
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: PMKSA-CACHE-REMOVED 7c:de:78:46:de:29 0
Jan 23 16:09:06 Qihe avahi-daemon[837]: Withdrawing address record for 10.131.81.201 on wlp1s0.
Jan 23 16:09:06 Qihe avahi-daemon[837]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 10.131.81.201.
Jan 23 16:09:06 Qihe avahi-daemon[837]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Jan 23 16:09:06 Qihe NetworkManager[847]: <info>  [1705997346.5498] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 16:09:06 Qihe systemd-resolved[825]: wlp1s0: Bus client reset DNS server list.
Jan 23 16:09:06 Qihe chronyd[1039]: Source 185.125.190.57 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 84.16.73.33 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 185.125.190.58 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 185.125.190.56 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 119.28.183.184 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 91.189.91.157 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Source 193.182.111.142 offline
Jan 23 16:09:06 Qihe chronyd[1039]: Can't synchronise: no selectable sources
Jan 23 16:09:06 Qihe chronyd[1039]: Source 202.112.31.197 offline
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jan 23 16:09:06 Qihe systemd[1]: Reached target Sleep.
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 23 16:09:06 Qihe systemd[1]: Starting Record successful boot for GRUB...
Jan 23 16:09:06 Qihe systemd[1]: Starting System Suspend...
Jan 23 16:09:06 Qihe systemd-sleep[26074]: Entering sleep state 'suspend'...
Jan 23 16:09:06 Qihe kernel: [23302.034224] PM: suspend entry (s2idle)
Jan 23 16:09:06 Qihe systemd[1]: grub-common.service: Deactivated successfully.
Jan 23 16:09:06 Qihe systemd[1]: Finished Record successful boot for GRUB.
Jan 23 16:09:06 Qihe systemd[1]: Starting GRUB failed boot detection...
Jan 23 16:09:06 Qihe kernel: [23302.051269] Filesystems sync: 0.017 seconds
Jan 23 16:09:06 Qihe wpa_supplicant[904]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 23 16:09:06 Qihe wpa_supplicant[904]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Jan 23 16:09:06 Qihe systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Jan 23 16:09:06 Qihe systemd[1]: Finished GRUB failed boot detection.
Jan 23 16:09:08 Qihe kernel: [23302.313692] Freezing user space processes
Jan 23 16:09:08 Qihe kernel: [23302.316456] Freezing user space processes completed (elapsed 0.002 seconds)
Jan 23 16:09:08 Qihe kernel: [23302.316459] OOM killer disabled.
Jan 23 16:09:08 Qihe kernel: [23302.316460] Freezing remaining freezable tasks
Jan 23 16:09:08 Qihe kernel: [23302.317735] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 23 16:09:08 Qihe kernel: [23302.317739] printk: Suspending console(s) (use no_console_suspend to debug)
Jan 23 16:09:08 Qihe kernel: [23302.985249] ACPI: EC: interrupt blocked
Jan 23 16:09:08 Qihe kernel: [23303.175205] amd_pmc AMDI0009:00: Last suspend didn't reach deepest state
Jan 23 16:09:08 Qihe kernel: [23303.176899] ACPI: EC: interrupt unblocked
Jan 23 16:09:08 Qihe kernel: [23303.365474] [drm] PCIE GART of 512M enabled (table at 0x0000008001500000).
Jan 23 16:09:08 Qihe kernel: [23303.365514] amdgpu 0000:c3:00.0: amdgpu: SMU is resuming...
Jan 23 16:09:08 Qihe kernel: [23303.368068] amdgpu 0000:c3:00.0: amdgpu: SMU is resumed successfully!
Jan 23 16:09:08 Qihe kernel: [23303.376619] nvme nvme0: Shutdown timeout set to 10 seconds
Jan 23 16:09:08 Qihe kernel: [23303.382022] nvme nvme0: 16/0/0 default/read/poll queues
Jan 23 16:09:08 Qihe kernel: [23303.848025] [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jan 23 16:09:08 Qihe kernel: [23303.848413] amdgpu 0000:c3:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Jan 23 16:09:08 Qihe kernel: [23303.848700] amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848703] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848705] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848706] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848707] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848708] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848709] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848710] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848712] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848713] amdgpu 0000:c3:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.848714] amdgpu 0000:c3:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jan 23 16:09:08 Qihe kernel: [23303.848715] amdgpu 0000:c3:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Jan 23 16:09:08 Qihe kernel: [23303.848716] amdgpu 0000:c3:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Jan 23 16:09:08 Qihe kernel: [23303.856115] [drm] ring gfx_32777.1.1 was added
Jan 23 16:09:08 Qihe kernel: [23303.856888] [drm] ring compute_32777.2.2 was added
Jan 23 16:09:08 Qihe kernel: [23303.857762] [drm] ring sdma_32777.3.3 was added
Jan 23 16:09:08 Qihe kernel: [23303.857796] [drm] ring gfx_32777.1.1 ib test pass
Jan 23 16:09:08 Qihe kernel: [23303.857830] [drm] ring compute_32777.2.2 ib test pass
Jan 23 16:09:08 Qihe kernel: [23303.858017] [drm] ring sdma_32777.3.3 ib test pass
Jan 23 16:09:08 Qihe kernel: [23303.865273] OOM killer enabled.
Jan 23 16:09:08 Qihe zed[910]: Exiting
Jan 23 16:09:08 Qihe acpid: input device has been disconnected, fd 16
Jan 23 16:09:08 Qihe systemd[1]: zfs-zed.service: Deactivated successfully.
Jan 23 16:09:08 Qihe kernel: [23303.865274] Restarting tasks ... done.
Jan 23 16:09:08 Qihe kernel: [23303.871289] random: crng reseeded on system resumption
Jan 23 16:09:08 Qihe systemd-sleep[26074]: System returned from sleep state.
Jan 23 16:09:08 Qihe bluetoothd[841]: Controller resume with wake event 0x0
Jan 23 16:09:08 Qihe kernel: [23303.968843] PM: suspend exit
Jan 23 16:09:08 Qihe systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 23 16:09:08 Qihe systemd[1]: Finished System Suspend.
Jan 23 16:09:08 Qihe systemd[1]: Stopped target Sleep.
Jan 23 16:09:08 Qihe systemd[1]: Reached target Suspend.
Jan 23 16:09:08 Qihe systemd[1]: Stopped target Suspend.
Jan 23 16:09:08 Qihe ModemManager[959]: <info>  [sleep-monitor-systemd] system is resuming
Jan 23 16:09:08 Qihe NetworkManager[847]: <info>  [1705997348.6048] manager: sleep: wake requested (sleeping: yes  enabled: yes)
output of `inxi -Fxxxrz`:

Code: Select all

System:
  Kernel: 6.5.0-14-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.18.1
    tk: Gtk 3.24.33 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 83AA v: YogaAir 14s APU8
    serial: <superuser required> Chassis: type: 10 v: YogaAir 14s APU8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76479 WIN
    serial: <superuser required> UEFI: LENOVO v: M6CN33WW date: 06/20/2023
Battery:
  ID-1: BAT0 charge: 70.8 Wh (99.6%) condition: 71.1/70.0 Wh (101.6%)
    volts: 17.8 min: 15.5 model: SMP L22M4PF7 type: Li-poly serial: <filter>
    status: Charging cycles: 26
CPU:
  Info: 8-core model: AMD Ryzen 7 7840S with Radeon 780M Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 3 rev: 1 cache: L1: 512 KiB L2: 8 MiB
    L3: 16 MiB
  Speed (MHz): avg: 1121 high: 4000
    min/max: 400/5132:6076:5289:5760:5918:5447:5605 cores: 1: 400 2: 400
    3: 4000 4: 400 5: 3548 6: 400 7: 2974 8: 400 9: 1484 10: 400 11: 400
    12: 400 13: 1543 14: 400 15: 400 16: 400 bogomips: 105408
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD vendor: Lenovo driver: amdgpu v: kernel pcie: speed: 16 GT/s
    lanes: 16 ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7 bus-ID: c3:00.0
    chip-ID: 1002:15bf class-ID: 0300
  Device-2: Luxvisions Innotech Integrated Camera type: USB
    driver: uvcvideo bus-ID: 3-1:2 chip-ID: 30c9:00a5 class-ID: fe01
    serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.18.0 driver:
    X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2944x1840 s-dpi: 96 s-size: 778x486mm (30.6x19.1")
    s-diag: 917mm (36.1")
  Monitor-1: eDP res: 2944x1840 hz: 90 dpi: 240 size: 312x195mm (12.3x7.7")
    diag: 368mm (14.5")
  OpenGL:
    renderer: GFX1103_R1 (gfx1103_r1 LLVM 15.0.7 DRM 3.54 6.5.0-14-generic)
    v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: c3:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
    vendor: Lenovo driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: c3:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: c3:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Sound Server-1: ALSA v: k6.5.0-14-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: MEDIATEK vendor: Lenovo driver: mt7921e v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 14c3:0616
    class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 1-5:2 chip-ID: 0489:e0d8 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.2 sub-v: 2209 hci-v: 5.2 rev: 820
Drives:
  Local Storage: total: 953.87 GiB used: 60.35 GiB (6.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: CL1QGXA7 temp: 37.9 C scheme: GPT
Partition:
  ID-1: / size: 74.54 GiB used: 24.27 GiB (32.6%) fs: ext4
    dev: /dev/nvme0n1p7
  ID-2: /boot/efi size: 256 MiB used: 43.1 MiB (16.8%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 134.11 GiB used: 10.88 GiB (8.1%) fs: ext4
    dev: /dev/nvme0n1p8
Swap:
  ID-1: swap-1 type: partition size: 30.52 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 34.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2961 apt: 2955 flatpak: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/cernbox-client.list
    1: deb http://cernbox.cern.ch/cernbox/doc/Linux/repo/Ubuntu_22.04/ /
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://mirrors.cqu.edu.cn/linuxmint virginia main upstream import backport
    2: deb http://mirrors.cqu.edu.cn/ubuntu jammy main restricted universe multiverse
    3: deb http://mirrors.cqu.edu.cn/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://mirrors.cqu.edu.cn/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 425 Uptime: 6h 16m wakeups: 22950 Memory: 27.18 GiB
  used: 4.19 GiB (15.4%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.4.0 alt: 11/12 Shell: fish v: 3.3.1 running-in: xfce4-terminal
  inxi: 3.3.13
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

zlinqi wrote: ⤴Tue Jan 23, 2024 4:23 amMy new laptop does not go into suspend state. Any idea how to fix it?
Welcome to the forum, zlinqi.

The data you posted indicates the computer did suspend.

Code: Select all

Jan 23 16:09:06 Qihe systemd[1]: Starting System Suspend...
Jan 23 16:09:06 Qihe systemd-sleep[26074]: Entering sleep state 'suspend'...
Jan 23 16:09:06 Qihe kernel: [23302.034224] PM: suspend entry (s2idle)
and then it resumed from suspend.

Code: Select all

Jan 23 16:09:08 Qihe bluetoothd[841]: Controller resume with wake event 0x0
Jan 23 16:09:08 Qihe kernel: [23303.968843] PM: suspend exit
Jan 23 16:09:08 Qihe systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 23 16:09:08 Qihe systemd[1]: Finished System Suspend.
Jan 23 16:09:08 Qihe systemd[1]: Stopped target Sleep.
Jan 23 16:09:08 Qihe systemd[1]: Reached target Suspend.
Jan 23 16:09:08 Qihe systemd[1]: Stopped target Suspend.
Please let us know what criteria you are using that is causing you to believe the computer did not suspend.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
zlinqi
Level 1
Level 1
Posts: 5
Joined: Tue Jan 23, 2024 4:06 am

Re: laptop does not go to suspend

Post by zlinqi »

Thanks a lot for the prompt reply. I don't consider it successfully suspended because a few seconds after I click the suspend button, the screen returns to the login screen...

Maybe the correct question is: what wakes it up?

The practical problem I'm facing is that when I travel, I just close the lid (it's configured to suspend when the laptop lid is closed in the power management), and the system seems to keep running and draining the battery -- and generating heat in my bag.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

zlinqi wrote: ⤴Tue Jan 23, 2024 11:47 pmThe practical problem I'm facing is that when I travel, I just close the lid (it's configured to suspend when the laptop lid is closed in the power management), and the system seems to keep running and draining the battery -- and generating heat in my bag.
Your computer only has the S2idle option (a Microsoft invention to make you think the operating system is resuming faster from suspend). That leaves more hardware powered than an S3 Sleep state. That will drain the battery more.
zlinqi wrote: ⤴Tue Jan 23, 2024 11:47 pmMaybe the correct question is: what wakes it up?
There is usually something hardware related which causes that to happen.

If this is the correct link, it appears the latest BIOS/UEFI is version 38. If you have a way to update, that may help. (UEFI is what gives the hardware instructions when being put to sleep.) You have very new hardware so there tends to be more updates early on until all the major problems noticed after the product was released are fixed.

Machine:
Type: Laptop System: LENOVO product: 83AA v: YogaAir 14s APU8
serial: <superuser required> Chassis: type: 10 v: YogaAir 14s APU8
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76479 WIN
serial: <superuser required> UEFI: LENOVO v: M6CN33WW date: 06/20/2023

Because of the very new hardware, it's possible the immediate wake-up is a graphics driver-related issue. You can see if newer firmware helps. I see several lines early in the "sleep" process related to the graphics driver.

Code: Select all

Jan 23 16:09:08 Qihe kernel: [23303.175205] amd_pmc AMDI0009:00: Last suspend didn't reach deepest state
Jan 23 16:09:08 Qihe kernel: [23303.176899] ACPI: EC: interrupt unblocked
Jan 23 16:09:08 Qihe kernel: [23303.365474] [drm] PCIE GART of 512M enabled (table at 0x0000008001500000).
Jan 23 16:09:08 Qihe kernel: [23303.365514] amdgpu 0000:c3:00.0: amdgpu: SMU is resuming...
Jan 23 16:09:08 Qihe kernel: [23303.368068] amdgpu 0000:c3:00.0: amdgpu: SMU is resumed successfully!
Here are instructions to update your system with the latest AMD driver linux-firmware.
  • Take a Timeshift snapshot. If this change causes problems, a snapshot will be the best way to reverse the change.
  • Please go to this page and download the linux-firmware-main.tar.gz firmware package into your Downloads directory. Make sure there is still a red rectangle with HEAD in it and a green rectangle with main in it. If not, stop and I will get you updated information.
  • Right-click the downloaded file and select "Extract here". That will create a directory named linux-firmware-main.
  • Navigate to the amdgpu folder in the linux-firmware-main directory just created and open a terminal in that amdgpu directory and run the following lines one at a time.

    Code: Select all

    sudo cp -u * /lib/firmware/amdgpu/
sudo update-initramfs -u -k all
  • Reboot the computer.
If you have any questions on the instructions, just ask.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

Moderator note: Term_Grecos's issue can now be found here IdeaPad Flex 5 14ARE05 does not suspend because the hardware is different. Suspend issues are hardware dependent.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
zlinqi
Level 1
Level 1
Posts: 5
Joined: Tue Jan 23, 2024 4:06 am

Re: laptop does not go to suspend

Post by zlinqi »

Thanks for the suggestions. I tried both updating the bios and the amdgpu, but the problem persisted.

Here is the new output of `inxi -Fxxxrz`:

Code: Select all

System:
  Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.18.1
    tk: Gtk 3.24.33 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 83AA v: YogaAir 14s APU8
    serial: <superuser required> Chassis: type: 10 v: YogaAir 14s APU8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76479 WIN
    serial: <superuser required> UEFI: LENOVO v: M6CN38WW date: 11/16/2023
Battery:
  ID-1: BAT0 charge: 66.3 Wh (94.4%) condition: 70.2/70.0 Wh (100.2%)
    volts: 17.5 min: 15.5 model: SMP L22M4PF7 type: Li-poly serial: <filter>
    status: Not charging cycles: 28
CPU:
  Info: 8-core model: AMD Ryzen 7 7840S with Radeon 780M Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 3 rev: 1 cache: L1: 512 KiB L2: 8 MiB
    L3: 16 MiB
  Speed (MHz): avg: 1556 high: 4521
    min/max: 400/5132:6076:5289:5760:5918:5447:5605 cores: 1: 2887 2: 400
    3: 1600 4: 400 5: 4521 6: 1962 7: 1621 8: 400 9: 2754 10: 400 11: 2215
    12: 400 13: 400 14: 400 15: 4148 16: 400 bogomips: 105410
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD vendor: Lenovo driver: amdgpu v: kernel pcie: speed: 16 GT/s
    lanes: 16 ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7 bus-ID: c3:00.0
    chip-ID: 1002:15bf class-ID: 0300
  Device-2: Luxvisions Innotech Integrated Camera type: USB
    driver: uvcvideo bus-ID: 3-1:2 chip-ID: 30c9:00a5 class-ID: fe01
    serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.18.0 driver:
    X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2944x1840 s-dpi: 96 s-size: 778x486mm (30.6x19.1")
    s-diag: 917mm (36.1")
  Monitor-1: eDP res: 2944x1840 hz: 90 dpi: 240 size: 312x195mm (12.3x7.7")
    diag: 368mm (14.5")
  OpenGL:
    renderer: GFX1103_R1 (gfx1103_r1 LLVM 15.0.7 DRM 3.54 6.5.0-15-generic)
    v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: c3:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
    vendor: Lenovo driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: c3:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: c3:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: MEDIATEK vendor: Lenovo driver: mt7921e v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 14c3:0616
    class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 1-5:2 chip-ID: 0489:e0d8 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.2 sub-v: 2209 hci-v: 5.2 rev: 820
Drives:
  Local Storage: total: 953.87 GiB used: 61.06 GiB (6.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: CL1QGXA7 temp: 36.9 C scheme: GPT
Partition:
  ID-1: / size: 74.54 GiB used: 24.99 GiB (33.5%) fs: ext4
    dev: /dev/nvme0n1p7
  ID-2: /boot/efi size: 256 MiB used: 43.1 MiB (16.8%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 134.11 GiB used: 10.87 GiB (8.1%) fs: ext4
    dev: /dev/nvme0n1p8
Swap:
  ID-1: swap-1 type: partition size: 30.52 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 35.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2969 apt: 2963 flatpak: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/cernbox-client.list
    1: deb http://cernbox.cern.ch/cernbox/doc/Linux/repo/Ubuntu_22.04/ /
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://mirrors.cqu.edu.cn/linuxmint virginia main upstream import backport
    2: deb http://mirrors.cqu.edu.cn/ubuntu jammy main restricted universe multiverse
    3: deb http://mirrors.cqu.edu.cn/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://mirrors.cqu.edu.cn/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 381 Uptime: 1h 18m wakeups: 32478 Memory: 27.18 GiB
  used: 2.63 GiB (9.7%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.4.0 alt: 11/12 Shell: fish v: 3.3.1 running-in: xfce4-terminal
  inxi: 3.3.13
and here is the log message in

Code: Select all

Jan 25 14:37:53 Qihe ModemManager[932]: <info>  [sleep-monitor-systemd] system is about to suspend
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.4908] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.4909] device (44:71:47:2F:D1:68): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.4911] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.4912] manager: NetworkManager state is now ASLEEP
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.4913] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 25 14:37:53 Qihe dbus-daemon[798]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=799 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 25 14:37:53 Qihe kernel: [ 4893.878206] ideapad_acpi VPC2004:00: Unknown event: 12
Jan 25 14:37:53 Qihe systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 25 14:37:53 Qihe dbus-daemon[798]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 25 14:37:53 Qihe systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 25 14:37:53 Qihe kernel: [ 4893.908341] wlp1s0: deauthenticating from 34:f7:16:4b:b0:27 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 25 14:37:53 Qihe wpa_supplicant[852]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=34:f7:16:4b:b0:27 reason=3 locally_generated=1
Jan 25 14:37:53 Qihe wpa_supplicant[852]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 25 14:37:53 Qihe wpa_supplicant[852]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.6950] device (wlp1s0): supplicant interface state: completed -> disconnected
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.6952] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 25 14:37:53 Qihe avahi-daemon[794]: Withdrawing address record for fe80::b00e:d126:536f:2fe3 on wlp1s0.
Jan 25 14:37:53 Qihe avahi-daemon[794]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::b00e:d126:536f:2fe3.
Jan 25 14:37:53 Qihe avahi-daemon[794]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.7342] dhcp4 (wlp1s0): canceled DHCP transaction
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.7342] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.7343] dhcp4 (wlp1s0): state changed no lease
Jan 25 14:37:53 Qihe avahi-daemon[794]: Withdrawing address record for 192.168.1.105 on wlp1s0.
Jan 25 14:37:53 Qihe avahi-daemon[794]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.1.105.
Jan 25 14:37:53 Qihe avahi-daemon[794]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Jan 25 14:37:53 Qihe systemd-resolved[790]: wlp1s0: Bus client set default route setting: no
Jan 25 14:37:53 Qihe systemd-resolved[790]: wlp1s0: Bus client reset DNS server list.
Jan 25 14:37:53 Qihe NetworkManager[799]: <info>  [1706164673.7836] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 25 14:37:53 Qihe chronyd[1008]: Source 193.182.111.142 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Source 91.189.91.157 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Source 185.125.190.57 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Source 185.209.85.222 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Source 185.125.190.58 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Source 84.16.67.12 offline
Jan 25 14:37:53 Qihe chronyd[1008]: Can't synchronise: no selectable sources
Jan 25 14:37:53 Qihe chronyd[1008]: Source 202.118.1.130 offline
Jan 25 14:37:53 Qihe wpa_supplicant[852]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 25 14:37:53 Qihe wpa_supplicant[852]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 25 14:37:53 Qihe wpa_supplicant[852]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Jan 25 14:37:54 Qihe systemd[1]: Reached target Sleep.
Jan 25 14:37:54 Qihe systemd[1]: Starting Record successful boot for GRUB...
Jan 25 14:37:54 Qihe systemd[1]: Starting System Suspend...
Jan 25 14:37:54 Qihe systemd-sleep[8219]: Entering sleep state 'suspend'...
Jan 25 14:37:54 Qihe kernel: [ 4894.612632] PM: suspend entry (s2idle)
Jan 25 14:37:54 Qihe systemd[1]: grub-common.service: Deactivated successfully.
Jan 25 14:37:54 Qihe systemd[1]: Finished Record successful boot for GRUB.
Jan 25 14:37:54 Qihe systemd[1]: Starting GRUB failed boot detection...
Jan 25 14:37:54 Qihe kernel: [ 4894.644732] Filesystems sync: 0.032 seconds
Jan 25 14:37:54 Qihe systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Jan 25 14:37:54 Qihe systemd[1]: Finished GRUB failed boot detection.
Jan 25 14:37:55 Qihe kernel: [ 4894.906954] Freezing user space processes
Jan 25 14:37:55 Qihe kernel: [ 4894.908969] Freezing user space processes completed (elapsed 0.002 seconds)
Jan 25 14:37:55 Qihe kernel: [ 4894.908972] OOM killer disabled.
Jan 25 14:37:55 Qihe kernel: [ 4894.908973] Freezing remaining freezable tasks
Jan 25 14:37:55 Qihe kernel: [ 4894.910126] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 25 14:37:55 Qihe kernel: [ 4894.910128] printk: Suspending console(s) (use no_console_suspend to debug)
Jan 25 14:37:55 Qihe kernel: [ 4895.144084] ACPI: EC: interrupt blocked
Jan 25 14:37:55 Qihe kernel: [ 4895.223086] amd_pmc AMDI0009:00: Last suspend didn't reach deepest state
Jan 25 14:37:55 Qihe kernel: [ 4895.224396] ACPI: EC: interrupt unblocked
Jan 25 14:37:55 Qihe kernel: [ 4895.417323] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
Jan 25 14:37:55 Qihe kernel: [ 4895.417372] amdgpu 0000:c3:00.0: amdgpu: SMU is resuming...
Jan 25 14:37:55 Qihe kernel: [ 4895.419965] amdgpu 0000:c3:00.0: amdgpu: SMU is resumed successfully!
Jan 25 14:37:55 Qihe kernel: [ 4895.428418] nvme nvme0: Shutdown timeout set to 10 seconds
Jan 25 14:37:55 Qihe kernel: [ 4895.433572] nvme nvme0: 16/0/0 default/read/poll queues
Jan 25 14:37:55 Qihe kernel: [ 4895.485170] [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jan 25 14:37:55 Qihe kernel: [ 4895.485423] amdgpu 0000:c3:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Jan 25 14:37:55 Qihe kernel: [ 4895.485708] amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485710] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485712] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485714] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485715] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485716] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485717] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485719] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485720] amdgpu 0000:c3:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485721] amdgpu 0000:c3:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.485722] amdgpu 0000:c3:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jan 25 14:37:55 Qihe kernel: [ 4895.485723] amdgpu 0000:c3:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Jan 25 14:37:55 Qihe kernel: [ 4895.485724] amdgpu 0000:c3:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Jan 25 14:37:55 Qihe kernel: [ 4895.490644] [drm] ring gfx_32774.1.1 was added
Jan 25 14:37:55 Qihe kernel: [ 4895.491249] [drm] ring compute_32774.2.2 was added
Jan 25 14:37:55 Qihe kernel: [ 4895.491810] [drm] ring sdma_32774.3.3 was added
Jan 25 14:37:55 Qihe kernel: [ 4895.491844] [drm] ring gfx_32774.1.1 ib test pass
Jan 25 14:37:55 Qihe kernel: [ 4895.491877] [drm] ring compute_32774.2.2 ib test pass
Jan 25 14:37:55 Qihe kernel: [ 4895.492006] [drm] ring sdma_32774.3.3 ib test pass
Jan 25 14:37:55 Qihe kernel: [ 4895.538350] OOM killer enabled.
Jan 25 14:37:55 Qihe kernel: [ 4895.538352] Restarting tasks ... done.
Jan 25 14:37:55 Qihe kernel: [ 4895.540604] random: crng reseeded on system resumption
Jan 25 14:37:55 Qihe acpid: input device has been disconnected, fd 16
Jan 25 14:37:55 Qihe systemd-sleep[8219]: System returned from sleep state.
Jan 25 14:37:55 Qihe bluetoothd[796]: Controller resume with wake event 0x0
Jan 25 14:37:55 Qihe kernel: [ 4895.645223] PM: suspend exit
Jan 25 14:37:55 Qihe systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 25 14:37:55 Qihe systemd[1]: Finished System Suspend.
Jan 25 14:37:55 Qihe systemd[1]: Stopped target Sleep.
Jan 25 14:37:55 Qihe systemd[1]: Reached target Suspend.
Jan 25 14:37:55 Qihe systemd[1]: Stopped target Suspend.
Jan 25 14:37:55 Qihe ModemManager[932]: <info>  [sleep-monitor-systemd] system is resuming
Jan 25 14:37:55 Qihe NetworkManager[799]: <info>  [1706164675.2939] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 25 14:37:55 Qihe NetworkManager[799]: <info>  [1706164675.2941] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
This is a dual-boot laptop. Windows can go to the suspend state I desire. One indication is the LED indicator on the power button is blinking instead of always-on.

I understand that as my hardware is new, thus I probably need to wait for a while until the relevant implementations are included in the new kernels.


BTW, I also notice some messages when updating the amdgpu:

Code: Select all

update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu
I guess this is not the culprit?
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

zlinqi wrote: ⤴Thu Jan 25, 2024 2:50 amBTW, I also notice some messages when updating the amdgpu:
None of those are your hardware so it does not matter they are missing.
zlinqi wrote: ⤴Thu Jan 25, 2024 2:50 amThanks for the suggestions. I tried both updating the bios and the amdgpu, but the problem persisted.
The other problem I've noticed on some laptops relates to the wifi driver. However, that usually leaves messages when it is a problem and I didn't see any.

The below is the only line seems suspicious, but for which I didn't find any information.

Code: Select all

Jan 25 14:37:53 Qihe kernel: [ 4893.878206] ideapad_acpi VPC2004:00: Unknown event: 12
zlinqi wrote: ⤴Thu Jan 25, 2024 2:50 amThis is a dual-boot laptop. Windows can go to the suspend state I desire. One indication is the LED indicator on the power button is blinking instead of always-on.
Have you checked the BIOS/UEFI settings to see if there is anything related to sleep?

I went searching through amdgpu bugs and found a lot of problems where the laptops were not waking up which seems to be the opposite problem.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
zlinqi
Level 1
Level 1
Posts: 5
Joined: Tue Jan 23, 2024 4:06 am

Re: laptop does not go to suspend

Post by zlinqi »

Thanks. Unfortunately, I don't find any sleep-related options in BIOS.

But sometimes I come across this authentication window when I lift the lid:
Image
Could this be related? Anything is preventing it from going to hibernate/sleep?
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

zlinqi wrote: ⤴Sat Jan 27, 2024 9:27 amBut sometimes I come across this authentication window when I lift the lid:
Image
Could this be related? Anything is preventing it from going to hibernate/sleep?
It likely is related.

Hibernation is saving to disk and shutting down the computer. That is different from sleep which is saving to RAM and requires the computer stay running.

Did you set up hibernation on your computer? Did you do anything to set up your computer to hibernate after it was suspended for a period of time?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
snakescrow
Level 1
Level 1
Posts: 1
Joined: Thu Mar 07, 2024 9:46 am

Re: laptop does not go to suspend

Post by snakescrow »

I also got lenovo yoga 14 slim 7 with the exactly same specs.

I got the same problem laptop goes to suspend but wakes up instantly my logs are also EXACTLY the same. I am using arch so its not distro related. I will probably be some package or hardware


https://bbs.archlinux.org/viewtopic.php?id=288637

in this article the guy had the same problem he fixed it with the udev rule so maybe it will help you but I got no idea how to create them.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

snakescrow wrote: ⤴Thu Mar 07, 2024 9:50 amhttps://bbs.archlinux.org/viewtopic.php?id=288637

in this article the guy had the same problem he fixed it with the udev rule so maybe it will help you but I got no idea how to create them.
Welcome to the forum, snakescrow.

That indicates that person's external usb keyboard was the issue. Are you or zlinqi using an external keyboard? If not, then the udev rule would not seem to apply to your situation.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
mark_herbert
Level 1
Level 1
Posts: 1
Joined: Mon Mar 18, 2024 10:45 am

Re: laptop does not go to suspend

Post by mark_herbert »

Yoga Air 14s APU8 is the Chineese version of global Yoga Slim 7 14APU8.

Same problem, it has ugly issue in BIOS that is not solved. It is possible however to override bad ACPI tables with the custom ones.

Please take a look in this issue

https://gitlab.freedesktop.org/drm/amd/-/issues/2812

Kernel is already fixed and starting from 6.6 it will work perfectly, but without replacing ACPI tables at boot it will not help.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: laptop does not go to suspend

Post by SMG »

mark_herbert wrote: ⤴Mon Mar 18, 2024 10:52 am Yoga Air 14s APU8 is the Chineese version of global Yoga Slim 7 14APU8.

Same problem, it has ugly issue in BIOS that is not solved. It is possible however to override bad ACPI tables with the custom ones.

Please take a look in this issue

https://gitlab.freedesktop.org/drm/amd/-/issues/2812

Kernel is already fixed and starting from 6.6 it will work perfectly, but without replacing ACPI tables at boot it will not help.
Welcome to the Linux Mint forum, mark_herbert.

I just finished reading the thread. :shock: You did A LOT of work to help with that issue. Hopefully, Lenovo will eventually fix the BIOS/UEFI, but great work from you and the others to come up with a workaround.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
zlinqi
Level 1
Level 1
Posts: 5
Joined: Tue Jan 23, 2024 4:06 am

Re: laptop does not go to suspend

Post by zlinqi »

Thanks a lot for the good news that the issue is understood! For the new kernels, I think I can just wait, they will come one day. But for the BIOS issue, will it be fixed by Lenovo? I mean, if they are notified and expressed the willingness to fix it?
Top
Post Reply

Return to “Hardware Support”