You are not logged in.

#1 2023-01-04 20:41:28

bttger
Member
Registered: 2023-01-04
Posts: 4

Suspend and hibernate system randomly stall with black screen

Sometimes (around every second or third time) my system hangs up with a black screen and the power light still on when I initiate system suspend or hibernate. I can't do anything then except pressing the power button for some seconds until it shuts down. To me it seems that the suspend and hibernate work properly since the abrupt shutdown leads to a journal recovery (on next boot) only when I try to suspend the system but not when I hibernate. The journalctl log confirms that I believe:

[tom:~] sudo journalctl -o short-precise -p 6 -r -b -1
Jan 04 19:51:51.792360 tom-v330 kernel: PM: suspend entry (deep)
Jan 04 19:51:51.790504 tom-v330 systemd-sleep[52245]: Entering sleep state 'suspend'...
Jan 04 19:51:51.768422 tom-v330 systemd[1]: Starting System Suspend...
Jan 04 19:51:51.751899 tom-v330 systemd[1]: Reached target Sleep.
Jan 04 19:51:51.753987 tom-v330 kernel: audit: type=1327 audit(1672858311.739:581): proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964
Jan 04 19:51:51.741005 tom-v330 kernel: audit: type=1300 audit(1672858311.739:581): arch=c000003e syscall=46 success=yes exit=492 a0=6 a1=7ffc4e2accb0 a2=0 a3=7ffc4e29bb5c items=0 ppid=1 pid=25375 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses>
Jan 04 19:51:51.740928 tom-v330 kernel: audit: type=1325 audit(1672858311.739:581): table=firewalld:22 family=1 entries=6 op=nft_unregister_rule pid=25375 comm="firewalld"
Jan 04 19:51:51.729119 tom-v330 NetworkManager[447]: <info>  [1672858311.7290] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.703607 tom-v330 kernel: audit: type=1327 audit(1672858311.695:580): proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964
Jan 04 19:51:51.703548 tom-v330 kernel: audit: type=1300 audit(1672858311.695:580): arch=c000003e syscall=46 success=yes exit=492 a0=6 a1=7ffc4e2accb0 a2=0 a3=7ffc4e29bb5c items=0 ppid=1 pid=25375 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses>
Jan 04 19:51:51.703447 tom-v330 kernel: audit: type=1325 audit(1672858311.695:580): table=firewalld:21 family=1 entries=6 op=nft_unregister_rule pid=25375 comm="firewalld"
Jan 04 19:51:51.692392 tom-v330 NetworkManager[447]: <info>  [1672858311.6923] dhcp6 (wlan0): state changed no lease
Jan 04 19:51:51.692373 tom-v330 NetworkManager[447]: <info>  [1672858311.6923] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jan 04 19:51:51.692354 tom-v330 NetworkManager[447]: <info>  [1672858311.6923] dhcp6 (wlan0): canceled DHCP transaction
Jan 04 19:51:51.692019 tom-v330 NetworkManager[447]: <info>  [1672858311.6920] dhcp4 (wlan0): state changed no lease
Jan 04 19:51:51.691994 tom-v330 NetworkManager[447]: <info>  [1672858311.6919] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jan 04 19:51:51.691960 tom-v330 NetworkManager[447]: <info>  [1672858311.6919] dhcp4 (wlan0): canceled DHCP transaction
Jan 04 19:51:51.678300 tom-v330 NetworkManager[447]: <info>  [1672858311.6782] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.678219 tom-v330 NetworkManager[447]: <info>  [1672858311.6781] device (wlan0): new IWD device state is disconnected
Jan 04 19:51:51.678045 tom-v330 NetworkManager[447]: <info>  [1672858311.6780] device (wlan0): new IWD device state is disconnecting
Jan 04 19:51:51.619888 tom-v330 kernel: wlan0: deauthenticating from 7c:8b:ca:c5:d8:dc by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 04 19:51:51.603933 tom-v330 kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Jan 04 19:51:51.600086 tom-v330 NetworkManager[447]: <info>  [1672858311.5999] device (enp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.517340 tom-v330 NetworkManager[447]: <info>  [1672858311.5173] dhcp6 (enp3s0): state changed no lease
Jan 04 19:51:51.517316 tom-v330 NetworkManager[447]: <info>  [1672858311.5173] dhcp6 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 04 19:51:51.517295 tom-v330 NetworkManager[447]: <info>  [1672858311.5172] dhcp6 (enp3s0): canceled DHCP transaction
Jan 04 19:51:51.516223 tom-v330 NetworkManager[447]: <info>  [1672858311.5162] dhcp4 (enp3s0): state changed no lease
Jan 04 19:51:51.516204 tom-v330 NetworkManager[447]: <info>  [1672858311.5161] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 04 19:51:51.515955 tom-v330 NetworkManager[447]: <info>  [1672858311.5159] dhcp4 (enp3s0): canceled DHCP transaction
Jan 04 19:51:51.507572 tom-v330 NetworkManager[447]: <info>  [1672858311.5075] device (enp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.486852 tom-v330 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 04 19:51:51.506202 tom-v330 kernel: audit: type=1130 audit(1672858311.486:579): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 04 19:51:51.486522 tom-v330 dbus-daemon[444]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 04 19:51:51.468530 tom-v330 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 04 19:51:51.428594 tom-v330 NetworkManager[447]: <info>  [1672858311.4285] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.424556 tom-v330 NetworkManager[447]: <info>  [1672858311.4245] device (enp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.423857 tom-v330 NetworkManager[447]: <info>  [1672858311.4237] manager: NetworkManager state is now ASLEEP
Jan 04 19:51:51.437556 tom-v330 dbus-daemon[444]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=447 comm="/usr/bin/NetworkManager --no-daemon")
Jan 04 19:51:51.421552 tom-v330 NetworkManager[447]: <info>  [1672858311.4214] device (/net/connman/iwd/0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 04 19:51:51.421282 tom-v330 NetworkManager[447]: <info>  [1672858311.4212] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 04 19:51:51.408026 tom-v330 systemd-logind[446]: The system will suspend now!
Jan 04 19:51:48.917889 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 04 19:51:38.677909 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 04 19:51:28.437896 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 04 19:51:18.198895 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random

My system info:

[tom:~] inxi -Fz
System:
  Kernel: 6.1.1-zen1-1-zen arch: x86_64 bits: 64 Desktop: GNOME v: 43.2
    Distro: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 81AX v: Lenovo V330-15IKB
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40697 WIN
    serial: <superuser required> UEFI: LENOVO v: 6SCN41WW date: 12/19/2018
CPU:
  Info: dual core model: Intel Core i3-7130U bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 500 min/max: 400/2700 cores: 1: 500 2: 500 3: 500 4: 500
Graphics:
  Device-1: Intel HD Graphics 620 driver: i915 v: kernel
  Device-2: SunplusIT Integrated Camera type: USB driver: uvcvideo
  Display: wayland server: X.org v: 1.21.1.6 with: Xwayland v: 22.1.7
    compositor: gnome-shell driver: gpu: i915 resolution: 1: 2560x1440~60Hz
    2: 1920x1080~60Hz
  API: EGL/GBM Message: No known Wayland EGL/GBM data sources.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
  Sound API: ALSA v: k6.1.1-zen1-1-zen running: yes
  Sound Server-1: PipeWire v: 0.3.63 running: yes
Network:
  Device-1: Intel Dual Band Wireless-AC 3165 Plus Bluetooth driver: iwlwifi
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: N/A type: USB driver: btusb
  Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
  Local Storage: total: 232.89 GiB used: 66.73 GiB (28.7%)
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
Partition:
  ID-1: / size: 227.63 GiB used: 66.57 GiB (29.2%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot size: 548.9 MiB used: 153.9 MiB (28.0%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 20.51 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 42.0 C pch: 34.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 226 Uptime: 1h 15m Memory: 7.11 GiB used: 3.61 GiB (50.9%)
  Shell: Zsh inxi: 3.3.24

Since this Arch install is quite new, I can not really tell whether this is a new issue or has been present since I have installed it on my laptop.

Does anyone here have an idea what could lead to that behavior or what steps I can take to identify the issue?

Last edited by bttger (2023-01-04 21:02:10)

Offline

#2 2023-01-04 23:25:41

walmartshopper
Member
Registered: 2010-03-31
Posts: 37

Re: Suspend and hibernate system randomly stall with black screen

Not sure if it's the same issue, but I have an intel tiger lake laptop that started having similar suspend issues after upgrading from kernel 6.0 to 6.1.  The screen would turn black but the cursor was still visible, and everything was hard frozen.  Interestingly I tried the 5.15 LTS kernel and it had the same issue, but kernel 6.0 works fine.  So maybe try an older kernel and see if anything changes.

Offline

#3 2023-01-05 02:14:59

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,132

Re: Suspend and hibernate system randomly stall with black screen

Anything different in the journal when it succeeds versus when it doesn't? Do you get the TPM complaints in both, for example?


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#4 2023-01-06 11:14:52

bttger
Member
Registered: 2023-01-04
Posts: 4

Re: Suspend and hibernate system randomly stall with black screen

I get the tpm compaints also when it succeeds.

Here is a log output for the case when I initiate hibernation and it fails to shut off the laptop:

Jan 06 00:55:48.282364 tom-v330 kernel: PM: hibernation: hibernation entry
Jan 06 00:55:48.281609 tom-v330 systemd-sleep[31239]: Entering sleep state 'hibernate'...
Jan 06 00:55:48.268177 tom-v330 systemd[1]: Starting Hibernate...
Jan 06 00:55:48.244461 tom-v330 systemd[1]: Reached target Sleep.
Jan 06 00:55:47.863253 tom-v330 google-chrome.desktop[1695]: [1686:1748:0106/005547.862678:ERROR:connection_factory_impl.cc(427)] Failed to connect to MCS endpoint with error -106
Jan 06 00:55:47.395895 tom-v330 kernel: audit: type=1327 audit(1672962947.394:277): proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964
Jan 06 00:55:47.395870 tom-v330 kernel: audit: type=1300 audit(1672962947.394:277): arch=c000003e syscall=46 success=yes exit=492 a0=6 a1=7ffc7d229290 a2=0 a3=7ffc7d21813c items=0 ppid=1 pid=527 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4>
Jan 06 00:55:47.395808 tom-v330 kernel: audit: type=1325 audit(1672962947.394:277): table=firewalld:16 family=1 entries=6 op=nft_unregister_rule pid=527 comm="firewalld"
Jan 06 00:55:47.353937 tom-v330 kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Jan 06 00:55:47.353581 tom-v330 NetworkManager[548]: <info>  [1672962947.3535] device (enp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 06 00:55:47.293413 tom-v330 NetworkManager[548]: <info>  [1672962947.2934] dhcp6 (enp3s0): state changed no lease
Jan 06 00:55:47.293402 tom-v330 NetworkManager[548]: <info>  [1672962947.2933] dhcp6 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 06 00:55:47.293388 tom-v330 NetworkManager[548]: <info>  [1672962947.2933] dhcp6 (enp3s0): canceled DHCP transaction
Jan 06 00:55:47.292973 tom-v330 NetworkManager[548]: <info>  [1672962947.2929] dhcp4 (enp3s0): state changed no lease
Jan 06 00:55:47.292952 tom-v330 NetworkManager[548]: <info>  [1672962947.2929] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 06 00:55:47.292926 tom-v330 NetworkManager[548]: <info>  [1672962947.2928] dhcp4 (enp3s0): canceled DHCP transaction
Jan 06 00:55:47.284876 tom-v330 kernel: audit: type=1130 audit(1672962947.282:276): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 06 00:55:47.284725 tom-v330 NetworkManager[548]: <info>  [1672962947.2847] device (enp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 06 00:55:47.283281 tom-v330 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 06 00:55:47.283042 tom-v330 dbus-daemon[516]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 06 00:55:47.272376 tom-v330 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 06 00:55:47.254333 tom-v330 dbus-daemon[516]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=548 comm="/usr/bin/NetworkManager --no-daemon")
Jan 06 00:55:47.249881 tom-v330 polkitd[618]: Unregistered Authentication Agent for unix-process:31206:10266483 (system bus name :1.107, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 06 00:55:47.246572 tom-v330 NetworkManager[548]: <info>  [1672962947.2465] device (enp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 06 00:55:47.245874 tom-v330 NetworkManager[548]: <info>  [1672962947.2458] manager: NetworkManager state is now ASLEEP
Jan 06 00:55:47.242335 tom-v330 NetworkManager[548]: <info>  [1672962947.2422] device (wlan0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 06 00:55:47.240845 tom-v330 NetworkManager[548]: <info>  [1672962947.2407] device (/net/connman/iwd/0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 06 00:55:47.240613 tom-v330 NetworkManager[548]: <info>  [1672962947.2405] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 06 00:55:47.231318 tom-v330 systemd-logind[521]: The system will hibernate now!
Jan 06 00:55:47.214110 tom-v330 polkitd[618]: Registered Authentication Agent for unix-process:31206:10266483 (system bus name :1.107 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 06 00:55:43.238990 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 06 00:55:32.998873 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 06 00:55:22.758939 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 06 00:55:12.518876 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random
Jan 06 00:55:02.278879 tom-v330 kernel: tpm tpm0: A TPM error (256) occurred attempting get random

I then hold the power button to forcefully shut it off. The next restart works normal and the state from before hibernation is successfully restored.

I will post a log output from a successful run later, but I believe they were identical.

Offline

#5 2023-01-06 14:55:26

SilentPuffer101
Member
Registered: 2016-07-21
Posts: 8

Re: Suspend and hibernate system randomly stall with black screen

This issue seems oddly similar to mine.

I have an Intel Tiger Lake Laptop (11th gen) and after upgrading (as of yesterday), suspend does not work anymore with similar symptoms and similar logs in the journal.
The laptop properly enters the S3 state but after resuming, I get an "unresponsive" black screen. I could still use SYSRQ to reboot but all else seems to be frozen, even I/O.
Suspend in linux-lts seem to work, though but I only have checked once.

Also back in October 2022, I have built a 6.1(rc7) kernel just for fun and suspend works just fine. Interestingly, suspend in that kernel does not work now.

Jan 06 20:59:42 NotALaptop kernel: Linux version 6.1.3-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 ZEN SMP PREEMPT_DYNAMIC Wed, 04 Jan 2023 16:28:>
Jan 06 20:59:42 NotALaptop kernel: microcode: microcode updated early to revision 0x42, date = 2022-06-28
-- Boot 1098a4b79ab3482b809edbd1ed72d504 --
Jan 06 20:58:01 NotALaptop kernel: PM: suspend entry (deep)
Jan 06 20:58:01 NotALaptop systemd-sleep[3256]: Entering sleep state 'suspend'...
Jan 06 20:58:01 NotALaptop systemd[1]: Starting System Suspend...
Jan 06 20:58:01 NotALaptop kernel: audit: type=1131 audit(1673009881.119:436): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/sys>
Jan 06 20:58:01 NotALaptop kernel: audit: type=1130 audit(1673009881.119:435): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/sys>
Jan 06 20:58:01 NotALaptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi>
Jan 06 20:58:01 NotALaptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
Jan 06 20:58:01 NotALaptop systemd[1]: Finished NVIDIA system suspend actions.
Jan 06 20:58:01 NotALaptop systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 06 20:58:00 NotALaptop kernel: audit: type=1130 audit(1673009880.029:434): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tccd-sleep comm="systemd" exe="/usr/lib/systemd/systemd>
Jan 06 20:58:00 NotALaptop systemd[1]: Reached target Sleep.
Jan 06 20:58:00 NotALaptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tccd-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Jan 06 20:58:00 NotALaptop systemd[1]: Finished TUXEDO Control Center Service (sleep/resume).
Jan 06 20:58:00 NotALaptop kernel: audit: type=1131 audit(1673009880.018:433): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tccd comm="systemd" exe="/usr/lib/systemd/systemd" host>
Jan 06 20:58:00 NotALaptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tccd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=>
Jan 06 20:58:00 NotALaptop systemd[1]: tccd.service: Consumed 3.632s CPU time.
Jan 06 20:58:00 NotALaptop systemd[1]: Stopped TUXEDO Control Center Service.
Jan 06 20:58:00 NotALaptop systemd[1]: tccd.service: Deactivated successfully.
Jan 06 20:58:00 NotALaptop tccd[3250]: Daemon is stopped
Jan 06 20:57:59 NotALaptop tccd[1486]: DisplayBacklightWorker: Save display brightness 100% (48000) on exit
Jan 06 20:57:59 NotALaptop tccd[1486]: SIGINT - Exiting
Jan 06 20:57:59 NotALaptop tccd[3250]: Stopping daemon..
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop kernel: ACPI Warning: Time parameter 200 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
Jan 06 20:57:59 NotALaptop systemd[1]: Stopping TUXEDO Control Center Service...
Jan 06 20:57:59 NotALaptop logger[3241]: <13>Jan  6 20:57:59 suspend: nvidia-suspend.service
Jan 06 20:57:59 NotALaptop suspend[3241]: nvidia-suspend.service
Jan 06 20:57:59 NotALaptop systemd[1]: Starting TUXEDO Control Center Service (sleep/resume)...
Jan 06 20:57:59 NotALaptop systemd[1]: Starting NVIDIA system suspend actions...

I've spent some time isolating the factors like disabling the Nvidia driver and any other recent tweaks but all of it are in vain as I did not found any solution.
(I do not consider using 5.15 kernel as a proper solution, sorry.)

Though, It seems weird that if I have an X11 session with compositing (KDE Plasma), the suspend/resume fails most of the time.
I honestly believed that this is an i915 firmware issue but I'll leave the test of that for another day. I'll use the 5.15 kernel for now.

Any thoughts?

Offline

Board footer

Powered by FluxBB