You are not logged in.

Pages: 1

#1 2024-12-03 09:24:20

kushiko
Member
Registered: 2024-12-03
Posts: 27

[SOLVED] The laptop itself suspends

Hey, everybody. Please help me, I'm a newbie. Please don't get angry if I answer stupidly. If I close the lid of my laptop, my laptop suspend. Then, I open the lid and the laptop starts to suspend on its own every ~20 seconds. What commands should I give you?

OS : Arch Linux x86_64
Kernel : Linux 6.12.1-arch1-1
WM : Hyprland (Wayland)

Last edited by kushiko (2024-12-08 14:15:10)

Offline

#2 2024-12-03 15:14:08

pvtvega
Member
Registered: 2024-11-25
Posts: 90

Re: [SOLVED] The laptop itself suspends

Hello, can you please start by providing some additional info. Firstly let's take a look at how your power management is configured:

cat /etc/systemd/logind.conf

Also please trigger the issue on your current boot and then provide the output of:

journalctl -b

Tell us what services you are using for power management:

systemctl list-units --type=service | grep -i power

And finally it couldn't hurt to see if there are any warnings or errors in the kernel logs:

sudo dmesg | grep -i acpi

Does the error occur only when you suspend the system by closing the lid? If you suspend via software or a sleep button or something does it also exhibit the same behaviour on wake?

Last edited by pvtvega (2024-12-03 15:14:33)

Offline

#3 2024-12-04 03:22:49

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

pvtvega wrote:

Hello, can you please start by providing some additional info. Firstly let's take a look at how your power management is configured:

cat /etc/systemd/logind.conf

Also please trigger the issue on your current boot and then provide the output of:

journalctl -b

Tell us what services you are using for power management:

systemctl list-units --type=service | grep -i power

And finally it couldn't hurt to see if there are any warnings or errors in the kernel logs:

sudo dmesg | grep -i acpi

Does the error occur only when you suspend the system by closing the lid? If you suspend via software or a sleep button or something does it also exhibit the same behaviour on wake?


Thank you for your answer. The fact is that this mistake does not always happen. So far, I haven't been able to catch it again to send you the command output. I will answer as soon as there is an error.

Offline

#4 2024-12-04 04:20:52

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

cat /etc/systemd/logind.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/logind.conf.d/ directory. The latter is generally
# recommended. Defaults can be restored by simply deleting the main
# configuration file and all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/logind.conf' to display the full config.
#
# See logind.conf(5) for details.

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#UserStopDelaySec=10
#SleepOperation=suspend-then-hibernate suspend
#HandlePowerKey=poweroff
#HandlePowerKeyLongPress=ignore
#HandleRebootKey=reboot
#HandleRebootKeyLongPress=poweroff
#HandleSuspendKey=suspend
#HandleSuspendKeyLongPress=hibernate
#HandleHibernateKey=hibernate
#HandleHibernateKeyLongPress=ignore
HandleLidSwitch=suspend
HandleLidSwitchExternalPower=suspend
HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#RebootKeyIgnoreInhibited=no
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RuntimeDirectoryInodesMax=
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
#StopIdleSessionSec=infinity
journalctl -b
дек 04 11:16:54 cyberlair wpa_supplicant[600]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
дек 04 11:16:54 cyberlair kernel: Filesystems sync: 0.014 seconds
дек 04 11:17:00 cyberlair kernel: Freezing user space processes
дек 04 11:17:00 cyberlair kernel: Freezing user space processes completed (elapsed 0.006 seconds)
дек 04 11:17:00 cyberlair kernel: OOM killer disabled.
дек 04 11:17:00 cyberlair kernel: Freezing remaining freezable tasks
дек 04 11:17:00 cyberlair kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
дек 04 11:17:00 cyberlair kernel: printk: Suspending console(s) (use no_console_suspend to debug)
дек 04 11:17:00 cyberlair kernel: ACPI: EC: interrupt blocked
дек 04 11:17:00 cyberlair kernel: ACPI: PM: Preparing to enter system sleep state S3
дек 04 11:17:00 cyberlair kernel: ACPI: EC: event blocked
дек 04 11:17:00 cyberlair kernel: ACPI: EC: EC stopped
дек 04 11:17:00 cyberlair kernel: ACPI: PM: Saving platform NVS memory
дек 04 11:17:00 cyberlair kernel: Disabling non-boot CPUs ...
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 11 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 10 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 9 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 8 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 7 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 6 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 5 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 4 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 3 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 2 is now offline
дек 04 11:17:00 cyberlair kernel: smpboot: CPU 1 is now offline
дек 04 11:17:00 cyberlair kernel: ACPI: PM: Low-level resume complete
дек 04 11:17:00 cyberlair kernel: ACPI: EC: EC started
дек 04 11:17:00 cyberlair kernel: ACPI: PM: Restoring platform NVS memory
дек 04 11:17:00 cyberlair kernel: Enabling non-boot CPUs ...
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
дек 04 11:17:00 cyberlair kernel: CPU1 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 2 APIC 0x8
дек 04 11:17:00 cyberlair kernel: CPU2 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 3 APIC 0x9
дек 04 11:17:00 cyberlair kernel: CPU3 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 4 APIC 0x10
дек 04 11:17:00 cyberlair kernel: CPU4 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 5 APIC 0x11
дек 04 11:17:00 cyberlair kernel: CPU5 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 6 APIC 0x18
дек 04 11:17:00 cyberlair kernel: CPU6 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 7 APIC 0x19
дек 04 11:17:00 cyberlair kernel: CPU7 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 8 APIC 0x28
дек 04 11:17:00 cyberlair kernel: core: cpu_atom PMU driver: PEBS-via-PT 
дек 04 11:17:00 cyberlair kernel: ... version:                5
дек 04 11:17:00 cyberlair kernel: ... bit width:              48
дек 04 11:17:00 cyberlair kernel: ... generic registers:      6
дек 04 11:17:00 cyberlair kernel: ... value mask:             0000ffffffffffff
дек 04 11:17:00 cyberlair kernel: ... max period:             00007fffffffffff
дек 04 11:17:00 cyberlair kernel: ... fixed-purpose events:   3
дек 04 11:17:00 cyberlair kernel: ... event mask:             000000070000003f
дек 04 11:17:00 cyberlair kernel: CPU8 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 9 APIC 0x2a
дек 04 11:17:00 cyberlair kernel: CPU9 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 10 APIC 0x2c
дек 04 11:17:00 cyberlair kernel: CPU10 is up
дек 04 11:17:00 cyberlair kernel: smpboot: Booting Node 0 Processor 11 APIC 0x2e
дек 04 11:17:00 cyberlair kernel: CPU11 is up
дек 04 11:17:00 cyberlair kernel: ACPI: PM: Waking up from system sleep state S3
дек 04 11:17:00 cyberlair kernel: ACPI: EC: interrupt unblocked
дек 04 11:17:00 cyberlair kernel: ACPI: EC: event unblocked
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.29.2
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
дек 04 11:17:00 cyberlair kernel: xhci_hcd 0000:00:0d.0: xHC error in resume, USBSTS 0x40
1, Reinit
дек 04 11:17:00 cyberlair kernel: usb usb1: root hub lost power or was reset
дек 04 11:17:00 cyberlair kernel: usb usb2: root hub lost power or was reset
дек 04 11:17:00 cyberlair kernel: nvme nvme0: 12/0/0 default/read/poll queues
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
дек 04 11:17:00 cyberlair kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
дек 04 11:17:00 cyberlair kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hd
cp_ops [i915])
дек 04 11:17:00 cyberlair kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp
_tee_component_ops [i915])
дек 04 11:17:00 cyberlair kernel: OOM killer enabled.
дек 04 11:17:00 cyberlair kernel: Restarting tasks ... done.
дек 04 11:17:00 cyberlair kernel: random: crng reseeded on system resumption
дек 04 11:17:00 cyberlair wpa_supplicant[600]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
дек 04 11:17:00 cyberlair wpa_supplicant[600]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
дек 04 11:17:00 cyberlair systemd-sleep[34210]: System returned from sleep operation 'suspend'.
дек 04 11:17:00 cyberlair kernel: PM: suspend exit
дек 04 11:17:00 cyberlair systemd-sleep[34210]: Successfully thawed unit 'user.slice'.
дек 04 11:17:00 cyberlair systemd[1]: systemd-suspend.service: Deactivated successfully.
дек 04 11:17:00 cyberlair systemd[1]: Finished System Suspend.
дек 04 11:17:00 cyberlair systemd[1]: Stopped target Sleep.
дек 04 11:17:00 cyberlair systemd[1]: Reached target Suspend.
дек 04 11:17:00 cyberlair systemd[1]: Stopped target Suspend.
дек 04 11:17:00 cyberlair systemd-logind[561]: Operation 'suspend' finished.
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5078] manager: sleep: wake requested (sleeping: yes  enabl
ed: yes)
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5080] device (wlan0): state change: unmanaged -> unavailab
le (reason 'managed', managed-type: 'external')
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5114] device (p2p-dev-wlan0): state change: unmanaged -> u
navailable (reason 'managed', managed-type: 'external')
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5128] manager: NetworkManager state is now DISCONNECTED
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5656] device (wlan0): supplicant interface state: internal
-starting -> disconnected
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5656] device (p2p-dev-wlan0): state change: unavailable ->
 unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5659] Wi-Fi P2P device controlled by interface wlan0 creat
ed
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5660] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P devic
e (/org/freedesktop/NetworkManager/Devices/10)
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5661] device (p2p-dev-wlan0): state change: unmanaged -> u
navailable (reason 'managed', managed-type: 'external')
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5663] device (wlan0): state change: unavailable -> disconn
ected (reason 'supplicant-available', managed-type: 'full')
дек 04 11:17:00 cyberlair NetworkManager[559]: <info>  [1733285820.5665] device (p2p-dev-wlan0): state change: unavailable ->
 disconnected (reason 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7387] policy: auto-activating connection 'RT-5GPON-44DE' (
44c54491-e8d7-43c4-b82a-a5f042048724)
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7390] device (wlan0): Activation: starting connection 'RT-
5GPON-44DE' (44c54491-e8d7-43c4-b82a-a5f042048724)
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7391] device (wlan0): state change: disconnected -> prepar
e (reason 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7392] manager: NetworkManager state is now CONNECTING
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7393] device (wlan0): state change: prepare -> config (rea
son 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7395] device (wlan0): Activation: (wifi) access point 'RT-
5GPON-44DE' has security, but secrets are required.
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7395] device (wlan0): state change: config -> need-auth (r
eason 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7402] device (wlan0): state change: need-auth -> prepare (
reason 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7403] device (wlan0): state change: prepare -> config (rea
son 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7404] device (wlan0): Activation: (wifi) connection 'RT-5G
PON-44DE' has security, and secrets exist.  No new secrets needed.
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7404] Config: added 'ssid' value 'RT-5GPON-44DE'
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7404] Config: added 'scan_ssid' value '1'
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7404] Config: added 'bgscan' value 'simple:30:-70:86400'
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7405] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA2
56 FT-PSK SAE FT-SAE'
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7405] Config: added 'auth_alg' value 'OPEN'
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7405] Config: added 'psk' value '<hidden>'
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: SME: Trying to authenticate with b4:e5:4c:96:44
:e3 (SSID='RT-5GPON-44DE' freq=5180 MHz)
дек 04 11:17:01 cyberlair kernel: wlan0: authenticate with b4:e5:4c:96:44:e3 (local address=c0:a5:e8:91:98:e4)
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7546] device (wlan0): supplicant interface state: disconne
cted -> authenticating
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7547] device (p2p-dev-wlan0): supplicant management interf
ace state: disconnected -> authenticating
дек 04 11:17:01 cyberlair kernel: wlan0: send auth to b4:e5:4c:96:44:e3 (try 1/3)
дек 04 11:17:01 cyberlair kernel: wlan0: authenticated
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: Trying to associate with b4:e5:4c:96:44:e3 (SSI
D='RT-5GPON-44DE' freq=5180 MHz)
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7813] device (wlan0): supplicant interface state: authenti
cating -> associating
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.7814] device (p2p-dev-wlan0): supplicant management interf
ace state: authenticating -> associating
дек 04 11:17:01 cyberlair kernel: wlan0: associate with b4:e5:4c:96:44:e3 (try 1/3)
дек 04 11:17:01 cyberlair kernel: wlan0: RX AssocResp from b4:e5:4c:96:44:e3 (capab=0x411 status=0 aid=1)
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: Associated with b4:e5:4c:96:44:e3
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
дек 04 11:17:01 cyberlair kernel: wlan0: associated
дек 04 11:17:01 cyberlair kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised b
y b4:e5:4c:96:44:e3
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: WPA: Key negotiation completed with b4:e5:4c:96
:44:e3 [PTK=CCMP GTK=TKIP]
дек 04 11:17:01 cyberlair wpa_supplicant[600]: wlan0: CTRL-EVENT-CONNECTED - Connection to b4:e5:4c:9
6:44:e3 completed [id=0 id_str=]
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.8837] device (wlan0): supplicant interface state: associat
ing -> completed
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.8838] device (wlan0): Activation: (wifi) Stage 2 of 5 (Dev
ice Configure) successful. Connected to wireless network "RT-5GPON-44DE"
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.8838] device (p2p-dev-wlan0): supplicant management interf
ace state: associating -> completed
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.8841] device (wlan0): state change: config -> ip-config (r
eason 'none', managed-type: 'full')
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.8848] dhcp4 (wlan0): activation: beginning transaction (ti
meout in 45 seconds)
дек 04 11:17:01 cyberlair NetworkManager[559]: <info>  [1733285821.9766] dhcp4 (wlan0): state changed new lease, address=192.
168.0.18, acd pending
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1371] dhcp4 (wlan0): state changed new lease, address=192.
168.0.18
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1376] policy: set 'RT-5GPON-44DE' (wlan0) as default for I
Pv4 routing and DNS
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1532] device (wlan0): state change: ip-config -> ip-check 
(reason 'none', managed-type: 'full')
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1564] device (wlan0): state change: ip-check -> secondarie
s (reason 'none', managed-type: 'full')
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1568] device (wlan0): state change: secondaries -> activat
ed (reason 'none', managed-type: 'full')
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1573] manager: NetworkManager state is now CONNECTED_SITE
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.1593] device (wlan0): Activation: successful, device activ
ated.
дек 04 11:17:02 cyberlair wpa_supplicant[600]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-47 noi
se=9999 txrate=234000
дек 04 11:17:02 cyberlair NetworkManager[559]: <info>  [1733285822.7591] manager: NetworkManager state is now CONNECTED_GLOBA
L
дек 04 11:17:03 cyberlair NetworkManager[559]: <info>  [1733285823.7052] dhcp6 (wlan0): activation: beginning transaction (ti
meout in 45 seconds)
дек 04 11:17:03 cyberlair NetworkManager[559]: <info>  [1733285823.7065] policy: set 'RT-5GPON-44DE' (wlan0) as default for I
Pv6 routing and DNS
дек 04 11:17:09 cyberlair systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
systemctl list-units --type=service | grep -i power
  upower.service                                        loaded active running Daemon for power management
sudo dmesg | grep -i acpi
[    0.014825] ACPI: SSDT 0x0000000043379000 002AA1 (v02 SaSsdt SaSsdt   00003000 INTL 20200717)
[    0.014827] ACPI: SSDT 0x0000000043375000 0033D3 (v02 INTEL  IgfxSsdt 00003000 INTL 20200717)
[    0.014829] ACPI: SSDT 0x0000000043367000 00D39F (v02 INTEL  TcssSsdt 00001000 INTL 20200717)
[    0.014830] ACPI: HPET 0x00000000433F9000 000038 (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014832] ACPI: APIC 0x0000000043366000 0001DC (v05 ALASKA A M I    01072009 AMI  01000013)
[    0.014834] ACPI: MCFG 0x0000000043365000 00003C (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014836] ACPI: SSDT 0x000000004335C000 008A17 (v02 ALASKA AdlP_Rvp 00001000 INTL 20200717)
[    0.014838] ACPI: SSDT 0x000000004335A000 001F1A (v02 ALASKA Ther_Rvp 00001000 INTL 20200717)
[    0.014839] ACPI: UEFI 0x000000004342A000 000048 (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014841] ACPI: NHLT 0x0000000043358000 001B37 (v00 ALASKA A M I    01072009 AMI  01000013)
[    0.014843] ACPI: LPIT 0x0000000043357000 0000CC (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014845] ACPI: SSDT 0x0000000043353000 002A83 (v02 ALASKA PtidDevc 00001000 INTL 20200717)
[    0.014847] ACPI: SSDT 0x0000000043350000 002357 (v02 ALASKA TbtTypeC 00000000 INTL 20200717)
[    0.014848] ACPI: DBGP 0x000000004334F000 000034 (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014850] ACPI: DBG2 0x000000004334E000 000054 (v00 ALASKA A M I    01072009 AMI  01000013)
[    0.014852] ACPI: SSDT 0x000000004334C000 001919 (v02 ALASKA UsbCTabl 00001000 INTL 20200717)
[    0.014854] ACPI: DMAR 0x000000004334B000 000088 (v02 INTEL  EDK2     00000002      01000013)
[    0.014856] ACPI: SSDT 0x000000004334A000 000BD8 (v02 INTEL  xh_adlLP 00000000 INTL 20200717)
[    0.014857] ACPI: SSDT 0x0000000043346000 003AEA (v02 SocGpe SocGpe   00003000 INTL 20200717)
[    0.014859] ACPI: SSDT 0x0000000043342000 0039DA (v02 SocCmn SocCmn   00003000 INTL 20200717)
[    0.014861] ACPI: SSDT 0x0000000043341000 000144 (v02 Intel  ADebTabl 00001000 INTL 20200717)
[    0.014863] ACPI: BGRT 0x0000000043340000 000038 (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.014865] ACPI: TPM2 0x000000004333F000 00004C (v04 ALASKA A M I    00000001 AMI  00000000)
[    0.014867] ACPI: PHAT 0x000000004333E000 0005B1 (v01 ALASKA A M I    00000005 MSFT 0100000D)
[    0.014868] ACPI: FPDT 0x000000004333D000 000044 (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.014870] ACPI: WSMT 0x0000000043356000 000028 (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.014872] ACPI: Reserving FACP table memory at [mem 0x433f6000-0x433f6113]
[    0.014873] ACPI: Reserving DSDT table memory at [mem 0x43383000-0x433f58b8]
[    0.014873] ACPI: Reserving FACS table memory at [mem 0x434d8000-0x434d803f]
[    0.014874] ACPI: Reserving SSDT table memory at [mem 0x433f7000-0x433f8473]
[    0.014874] ACPI: Reserving FIDT table memory at [mem 0x43382000-0x4338209b]
[    0.014875] ACPI: Reserving SSDT table memory at [mem 0x433fa000-0x433fa38b]
[    0.014875] ACPI: Reserving SSDT table memory at [mem 0x4337c000-0x43381d00]
[    0.014876] ACPI: Reserving SSDT table memory at [mem 0x43379000-0x4337baa0]
[    0.014876] ACPI: Reserving SSDT table memory at [mem 0x43375000-0x433783d2]
[    0.014877] ACPI: Reserving SSDT table memory at [mem 0x43367000-0x4337439e]
[    0.014877] ACPI: Reserving HPET table memory at [mem 0x433f9000-0x433f9037]
[    0.014878] ACPI: Reserving APIC table memory at [mem 0x43366000-0x433661db]
[    0.014878] ACPI: Reserving MCFG table memory at [mem 0x43365000-0x4336503b]
[    0.014879] ACPI: Reserving SSDT table memory at [mem 0x4335c000-0x43364a16]
[    0.014879] ACPI: Reserving SSDT table memory at [mem 0x4335a000-0x4335bf19]
[    0.014879] ACPI: Reserving UEFI table memory at [mem 0x4342a000-0x4342a047]
[    0.014880] ACPI: Reserving NHLT table memory at [mem 0x43358000-0x43359b36]
[    0.014880] ACPI: Reserving LPIT table memory at [mem 0x43357000-0x433570cb]
[    0.014881] ACPI: Reserving SSDT table memory at [mem 0x43353000-0x43355a82]
[    0.014881] ACPI: Reserving SSDT table memory at [mem 0x43350000-0x43352356]
[    0.014882] ACPI: Reserving DBGP table memory at [mem 0x4334f000-0x4334f033]
[    0.014882] ACPI: Reserving DBG2 table memory at [mem 0x4334e000-0x4334e053]
[    0.014883] ACPI: Reserving SSDT table memory at [mem 0x4334c000-0x4334d918]
[    0.014883] ACPI: Reserving DMAR table memory at [mem 0x4334b000-0x4334b087]
[    0.014884] ACPI: Reserving SSDT table memory at [mem 0x4334a000-0x4334abd7]
[    0.014884] ACPI: Reserving SSDT table memory at [mem 0x43346000-0x43349ae9]
[    0.014885] ACPI: Reserving SSDT table memory at [mem 0x43342000-0x433459d9]
[    0.014885] ACPI: Reserving SSDT table memory at [mem 0x43341000-0x43341143]
[    0.014886] ACPI: Reserving BGRT table memory at [mem 0x43340000-0x43340037]
[    0.014886] ACPI: Reserving TPM2 table memory at [mem 0x4333f000-0x4333f04b]
[    0.014886] ACPI: Reserving PHAT table memory at [mem 0x4333e000-0x4333e5b0]
[    0.014887] ACPI: Reserving FPDT table memory at [mem 0x4333d000-0x4333d043]
[    0.014887] ACPI: Reserving WSMT table memory at [mem 0x43356000-0x43356027]
[    0.034777] ACPI: PM-Timer IO Port: 0x1808
[    0.034782] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.034784] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.034784] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.034784] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.034785] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.034785] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.034786] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.034786] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.034787] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
[    0.034787] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
[    0.034787] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
[    0.034788] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
[    0.034788] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
[    0.034789] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
[    0.034789] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
[    0.034789] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
[    0.034790] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
[    0.034790] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
[    0.034791] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
[    0.034791] ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
[    0.034792] ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1])
[    0.034792] ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1])
[    0.034792] ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1])
[    0.034793] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.034913] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.034915] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.034917] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.034918] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.080202] ACPI: Core revision 20240827
[    0.114332] ACPI: PM: Registering ACPI NVS region [mem 0x433fb000-0x434d8fff] (909312 bytes)
[    0.115167] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.120689] ACPI: Added _OSI(Module Device)
[    0.120689] ACPI: Added _OSI(Processor Device)
[    0.120689] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.120689] ACPI: Added _OSI(Processor Aggregator Device)
[    0.209934] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.209940] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.209942] ACPI: Skipping parse of AML opcode: Method (0x0014)
[    0.209944] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.209947] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.209949] ACPI: Skipping parse of AML opcode: Method (0x0014)
[    0.212177] ACPI: 16 ACPI AML tables successfully acquired and loaded
[    0.218293] ACPI Error: Needed [Integer/String/Buffer], found [Package] (____ptrval____) (20240827/exresop-469)
[    0.218299] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    0.218304] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    0.218307] ACPI Error: Method execution failed \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/uteval-68)
[    0.231037] ACPI: Dynamic OEM Table Load:
[    0.231046] ACPI: SSDT 0xFFFF9D98814E1C00 000394 (v02 PmRef  Cpu0Cst  00003001 INTL 20200717)
[    0.232134] ACPI: Dynamic OEM Table Load:
[    0.232140] ACPI: SSDT 0xFFFF9D98814DA000 0005E4 (v02 PmRef  Cpu0Ist  00003000 INTL 20200717)
[    0.233259] ACPI: Dynamic OEM Table Load:
[    0.233263] ACPI: SSDT 0xFFFF9D98825BF800 0001AB (v02 PmRef  Cpu0Psd  00003000 INTL 20200717)
[    0.234287] ACPI: Dynamic OEM Table Load:
[    0.234292] ACPI: SSDT 0xFFFF9D98814D8800 000476 (v02 PmRef  Cpu0Hwp  00003000 INTL 20200717)
[    0.235732] ACPI: Dynamic OEM Table Load:
[    0.235740] ACPI: SSDT 0xFFFF9D98814D4000 001BAF (v02 PmRef  ApIst    00003000 INTL 20200717)
[    0.237535] ACPI: Dynamic OEM Table Load:
[    0.237541] ACPI: SSDT 0xFFFF9D98814D6000 001038 (v02 PmRef  ApHwp    00003000 INTL 20200717)
[    0.239100] ACPI: Dynamic OEM Table Load:
[    0.239106] ACPI: SSDT 0xFFFF9D98814D0000 001349 (v02 PmRef  ApPsd    00003000 INTL 20200717)
[    0.240704] ACPI: Dynamic OEM Table Load:
[    0.240710] ACPI: SSDT 0xFFFF9D98814EF000 000FBB (v02 PmRef  ApCst    00003000 INTL 20200717)
[    0.245896] ACPI: EC: EC started
[    0.245898] ACPI: EC: interrupt blocked
[    0.246904] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.246907] ACPI: \_SB_.PC00.LPCB.H_EC: Boot DSDT EC used to handle transactions
[    0.246908] ACPI: Interpreter enabled
[    0.246955] ACPI: PM: (supports S0 S3 S4 S5)
[    0.246956] ACPI: Using IOAPIC for interrupt routing
[    0.248240] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.249602] ACPI: Enabled 8 GPEs in block 00 to 7F
[    0.250565] ACPI: \_SB_.PC00.PEG1.PXP_: New power resource
[    0.252108] ACPI Error: Needed [Integer/String/Buffer], found [Package] (____ptrval____) (20240827/exresop-469)
[    0.252111] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    0.252115] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    0.253751] ACPI: \_SB_.PC00.RP09.PXP_: New power resource
[    0.260255] ACPI: \_SB_.PC00.RP06.PXP_: New power resource
[    0.261533] ACPI: \_SB_.PC00.RP08.PXP_: New power resource
[    0.269264] ACPI: \_SB_.PC00.XHCI.RHUB.HS10.BTRT: New power resource
[    0.269939] ACPI: \_SB_.PC00.PAUD: New power resource
[    0.279624] ACPI: \_SB_.PC00.CNVW.WRST: New power resource
[    0.287322] ACPI: \_SB_.PC00.TBT0: New power resource
[    0.287623] ACPI: \_SB_.PC00.TBT1: New power resource
[    0.287916] ACPI: \_SB_.PC00.D3C_: New power resource
[    0.329337] ACPI: \_TZ_.FN00: New power resource
[    0.329392] ACPI: \_TZ_.FN01: New power resource
[    0.329443] ACPI: \_TZ_.FN02: New power resource
[    0.329495] ACPI: \_TZ_.FN03: New power resource
[    0.329546] ACPI: \_TZ_.FN04: New power resource
[    0.330029] ACPI: \PIN_: New power resource
[    0.330583] ACPI: PCI Root Bridge [PC00] (domain 0000 [bus 00-fe])
[    0.330589] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.333112] acpi PNP0A08:00: _OSC: platform does not support [AER]
[    0.338087] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR DPC]
[    0.358205] ACPI Error: Needed [Integer/String/Buffer], found [Package] (____ptrval____) (20240827/exresop-469)
[    0.358209] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    0.358213] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    0.364114] ACPI: PCI: Interrupt link LNKA configured for IRQ 0
[    0.364213] ACPI: PCI: Interrupt link LNKB configured for IRQ 1
[    0.364309] ACPI: PCI: Interrupt link LNKC configured for IRQ 0
[    0.364404] ACPI: PCI: Interrupt link LNKD configured for IRQ 0
[    0.364498] ACPI: PCI: Interrupt link LNKE configured for IRQ 0
[    0.364593] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    0.364688] ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[    0.364783] ACPI: PCI: Interrupt link LNKH configured for IRQ 0
[    0.380145] ACPI: EC: interrupt unblocked
[    0.380146] ACPI: EC: event unblocked
[    0.380298] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.380298] ACPI: EC: GPE=0x6e
[    0.380298] ACPI: \_SB_.PC00.LPCB.H_EC: Boot DSDT EC initialization complete
[    0.380298] ACPI: \_SB_.PC00.LPCB.H_EC: EC: Used to handle transactions and events
[    0.380416] ACPI: bus type USB registered
[    0.383882] PCI: Using ACPI for IRQ routing
[    0.517492] pnp: PnP ACPI init
[    0.517584] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000b69d9fea (20240827/exresop-469)
[    0.517588] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    0.517593] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    0.517596] ACPI Error: Method execution failed \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/uteval-68)
[    0.524345] pnp: PnP ACPI: found 6 devices
[    0.529817] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.580518] ACPI: AC: AC Adapter [AC0] (on-line)
[    0.583655] ACPI: button: Lid Switch [LID0]
[    0.583712] ACPI: button: Power Button [PWRB]
[    0.583839] ACPI: button: Power Button [PWRF]
[    0.587334] ACPI: thermal: Thermal Zone [TZ00] (28 C)
[    0.589365] hpet_acpi_add: no address or irqs in _CRS
[    0.620661] ACPI: bus type drm_connector registered
[    0.627582] ACPI: battery: Slot [BAT0] (battery present)
[    0.647173] acpi device:98: hash matches
[    0.647179] acpi device:6b: hash matches
[    1.124569] ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    3.311004] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000b69d9fea (20240827/exresop-469)
[    3.311010] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    3.311015] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    3.320975] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000b69d9fea (20240827/exresop-469)
[    3.320980] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    3.320983] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[    3.326623] ACPI Error: Needed [Integer/String/Buffer], found [Package] 00000000b69d9fea (20240827/exresop-469)
[    3.326627] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [LEqual] (20240827/dswexec-433)
[    3.326631] ACPI Error: Aborting method \_SB.PC00.PEG0._STA due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
[ 2289.508534] ACPI: EC: interrupt blocked
[ 2289.534187] ACPI: PM: Preparing to enter system sleep state S3
[ 2289.541697] ACPI: EC: event blocked
[ 2289.541698] ACPI: EC: EC stopped
[ 2289.541698] ACPI: PM: Saving platform NVS memory
[ 2289.578240] ACPI: PM: Low-level resume complete
[ 2289.578451] ACPI: EC: EC started
[ 2289.578452] ACPI: PM: Restoring platform NVS memory
[ 2289.651648] ACPI: PM: Waking up from system sleep state S3
[ 2289.657566] ACPI: EC: interrupt unblocked
[ 2289.686184] ACPI: EC: event unblocked
[ 2319.865536] ACPI: EC: interrupt blocked
[ 2319.891212] ACPI: PM: Preparing to enter system sleep state S3
[ 2319.897507] ACPI: EC: event blocked
[ 2319.897507] ACPI: EC: EC stopped
[ 2319.897508] ACPI: PM: Saving platform NVS memory
[ 2319.932733] ACPI: PM: Low-level resume complete
[ 2319.932942] ACPI: EC: EC started
[ 2319.932943] ACPI: PM: Restoring platform NVS memory
[ 2320.003986] ACPI: PM: Waking up from system sleep state S3
[ 2320.009916] ACPI: EC: interrupt unblocked
[ 2320.042092] ACPI: EC: event unblocked
[ 2350.142399] ACPI: EC: interrupt blocked
[ 2350.167923] ACPI: PM: Preparing to enter system sleep state S3
[ 2350.177567] ACPI: EC: event blocked
[ 2350.177568] ACPI: EC: EC stopped
[ 2350.177568] ACPI: PM: Saving platform NVS memory
[ 2350.212778] ACPI: PM: Low-level resume complete
[ 2350.212929] ACPI: EC: EC started
[ 2350.212929] ACPI: PM: Restoring platform NVS memory
[ 2350.285811] ACPI: PM: Waking up from system sleep state S3
[ 2350.294618] ACPI: EC: interrupt unblocked
[ 2350.329362] ACPI: EC: event unblocked
[ 2380.701557] ACPI: EC: interrupt blocked
[ 2380.728830] ACPI: PM: Preparing to enter system sleep state S3
[ 2380.742161] ACPI: EC: event blocked
[ 2380.742164] ACPI: EC: EC stopped
[ 2380.742164] ACPI: PM: Saving platform NVS memory
[ 2380.788721] ACPI: PM: Low-level resume complete
[ 2380.788938] ACPI: EC: EC started
[ 2380.788938] ACPI: PM: Restoring platform NVS memory
[ 2380.876147] ACPI: PM: Waking up from system sleep state S3
[ 2380.885862] ACPI: EC: interrupt unblocked
[ 2380.919252] ACPI: EC: event unblocked
[ 2411.225272] ACPI: EC: interrupt blocked
[ 2411.250796] ACPI: PM: Preparing to enter system sleep state S3
[ 2411.258765] ACPI: EC: event blocked
[ 2411.258767] ACPI: EC: EC stopped
[ 2411.258768] ACPI: PM: Saving platform NVS memory
[ 2411.298144] ACPI: PM: Low-level resume complete
[ 2411.298354] ACPI: EC: EC started
[ 2411.298355] ACPI: PM: Restoring platform NVS memory
[ 2411.370423] ACPI: PM: Waking up from system sleep state S3
[ 2411.377799] ACPI: EC: interrupt unblocked
[ 2411.412154] ACPI: EC: event unblocked
[ 2442.018067] ACPI: EC: interrupt blocked
[ 2442.043663] ACPI: PM: Preparing to enter system sleep state S3
[ 2442.053543] ACPI: EC: event blocked
[ 2442.053544] ACPI: EC: EC stopped
[ 2442.053544] ACPI: PM: Saving platform NVS memory
[ 2442.093438] ACPI: PM: Low-level resume complete
[ 2442.093648] ACPI: EC: EC started
[ 2442.093648] ACPI: PM: Restoring platform NVS memory
[ 2442.167350] ACPI: PM: Waking up from system sleep state S3
[ 2442.174705] ACPI: EC: interrupt unblocked
[ 2442.207983] ACPI: EC: event unblocked
[ 2472.514950] ACPI: EC: interrupt blocked
[ 2472.540571] ACPI: PM: Preparing to enter system sleep state S3
[ 2472.551694] ACPI: EC: event blocked
[ 2472.551695] ACPI: EC: EC stopped
[ 2472.551695] ACPI: PM: Saving platform NVS memory
[ 2472.592472] ACPI: PM: Low-level resume complete
[ 2472.592559] ACPI: EC: EC started
[ 2472.592559] ACPI: PM: Restoring platform NVS memory
[ 2472.663067] ACPI: PM: Waking up from system sleep state S3
[ 2472.670154] ACPI: EC: interrupt unblocked
[ 2472.703708] ACPI: EC: event unblocked
[ 2503.000855] ACPI: EC: interrupt blocked
[ 2503.026640] ACPI: PM: Preparing to enter system sleep state S3
[ 2503.036120] ACPI: EC: event blocked
[ 2503.036121] ACPI: EC: EC stopped
[ 2503.036121] ACPI: PM: Saving platform NVS memory
[ 2503.075815] ACPI: PM: Low-level resume complete
[ 2503.075901] ACPI: EC: EC started
[ 2503.075902] ACPI: PM: Restoring platform NVS memory
[ 2503.152278] ACPI: PM: Waking up from system sleep state S3
[ 2503.160091] ACPI: EC: interrupt unblocked
[ 2503.192854] ACPI: EC: event unblocked
[ 2533.682607] ACPI: EC: interrupt blocked
[ 2533.708242] ACPI: PM: Preparing to enter system sleep state S3
[ 2533.717906] ACPI: EC: event blocked
[ 2533.717907] ACPI: EC: EC stopped
[ 2533.717907] ACPI: PM: Saving platform NVS memory
[ 2533.757464] ACPI: PM: Low-level resume complete
[ 2533.757674] ACPI: EC: EC started
[ 2533.757675] ACPI: PM: Restoring platform NVS memory
[ 2533.828660] ACPI: PM: Waking up from system sleep state S3
[ 2533.835326] ACPI: EC: interrupt unblocked
[ 2533.865215] ACPI: EC: event unblocked
[ 2564.327308] ACPI: EC: interrupt blocked
[ 2564.352782] ACPI: PM: Preparing to enter system sleep state S3
[ 2564.362451] ACPI: EC: event blocked
[ 2564.362452] ACPI: EC: EC stopped
[ 2564.362453] ACPI: PM: Saving platform NVS memory
[ 2564.402295] ACPI: PM: Low-level resume complete
[ 2564.402381] ACPI: EC: EC started
[ 2564.402382] ACPI: PM: Restoring platform NVS memory
[ 2564.480658] ACPI: PM: Waking up from system sleep state S3
[ 2564.486795] ACPI: EC: interrupt unblocked
[ 2564.522397] ACPI: EC: event unblocked
[ 2595.041643] ACPI: EC: interrupt blocked
[ 2595.067293] ACPI: PM: Preparing to enter system sleep state S3
[ 2595.077747] ACPI: EC: event blocked
[ 2595.077750] ACPI: EC: EC stopped
[ 2595.077750] ACPI: PM: Saving platform NVS memory
[ 2595.118839] ACPI: PM: Low-level resume complete
[ 2595.118929] ACPI: EC: EC started
[ 2595.118929] ACPI: PM: Restoring platform NVS memory
[ 2595.193660] ACPI: PM: Waking up from system sleep state S3
[ 2595.202306] ACPI: EC: interrupt unblocked
[ 2595.236924] ACPI: EC: event unblocked
[ 2625.599774] ACPI: EC: interrupt blocked
[ 2625.625233] ACPI: PM: Preparing to enter system sleep state S3
[ 2625.632910] ACPI: EC: event blocked
[ 2625.632911] ACPI: EC: EC stopped
[ 2625.632912] ACPI: PM: Saving platform NVS memory
[ 2625.672974] ACPI: PM: Low-level resume complete
[ 2625.673184] ACPI: EC: EC started
[ 2625.673185] ACPI: PM: Restoring platform NVS memory
[ 2625.743812] ACPI: PM: Waking up from system sleep state S3
[ 2625.752803] ACPI: EC: interrupt unblocked
[ 2625.784925] ACPI: EC: event unblocked

Error not observed when using systemctl in the terminal

Last edited by kushiko (2024-12-04 04:28:56)

Offline

#5 2024-12-04 06:20:10

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

Please don't copy-paste out of the pager, it's only a segment of the journal and the lines are hard-wrapped.
Try 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

You can also access previous boots

sudo journalctl -b -3 | curl -F 'file=@-' 0x0.st

for three boots ago.

This looks like it might be an incident?

[ 2320.003986] ACPI: PM: Waking up from system sleep state S3
[ 2320.009916] ACPI: EC: interrupt unblocked
[ 2320.042092] ACPI: EC: event unblocked
[ 2350.142399] ACPI: EC: interrupt blocked
[ 2350.167923] ACPI: PM: Preparing to enter system sleep state S3

The delay is likely controlled by

#HoldoffTimeoutSec=30s

what means the lid probably keeps firing.
Is this a lenovo notebook?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2024-12-04 06:41:33

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

Is this a lenovo notebook?

No. I have a Maibenben laptop

Offline

#7 2024-12-04 14:33:55

pvtvega
Member
Registered: 2024-11-25
Posts: 90

Re: [SOLVED] The laptop itself suspends

To expand on what Seth said, if you look at the ACPI entries in the kernel log, you can see:

[ 2320.003986] ACPI: PM: Waking up from system sleep state S3
...
...
...
[ 2350.167923] ACPI: PM: Preparing to enter system sleep state S3

Where 2320 and 2350 are the time in seconds. Notice the gap between them is 30, and your 

#HoldoffTimeoutSec=30s

parameter in logind.conf is also set to 30. The purpose of this parameter is to ignore subsequent suspend/hibernate/power requests if another one is sent within 30 seconds of the previous request. The fact that the system is consistently entering sleep state 30 seconds after leaving suggests that it's continuously receiving a request to enter sleep (maybe from a faulty lid switch?) and it's the HoldOffTimeOutSec parameter that's regulating how often the system obeys that command.

This is why in my original reply I asked:

pvtvega wrote:

Does the error occur only when you suspend the system by closing the lid? If you suspend via software or a sleep button or something does it also exhibit the same behaviour on wake?

Because the answer will help determine if this is a software or hardware issue.

Offline

#8 2024-12-04 14:41:09

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

pvtvega wrote:

Because the answer will help determine if this is a software or hardware issue.

Should I just uncomment this line?

Last edited by kushiko (2024-12-04 14:42:26)

Offline

#9 2024-12-04 14:45:05

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

Asking because lenovo lids have recently been acting up a lot.
Please make sure to produce the relevant system journals, but if the lid button indeed fires wildly (you could inspect it w/ acpid, https://wiki.archlinux.org/title/Acpid ) there's little you could do about that except maybe raising the HoldoffTimeoutSec to some minutes (ifff the lid stops at some point)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#10 2024-12-04 14:46:03

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

Asking because lenovo lids have recently been acting up a lot.
Please make sure to produce the relevant system journals, but if the lid button indeed fires wildly (you could inspect it w/ acpid, https://wiki.archlinux.org/title/Acpid ) there's little you could do about that except maybe raising the HoldoffTimeoutSec to some minutes (ifff the lid stops at some point)

So it's a fault in the cover itself? It's kind of shorting out?

Offline

#11 2024-12-04 15:14:05

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

We won't know what's going on until you post a complet journal covering the incident, experiment w/ the holdoff timeout or monitor events w/ acpid, but it is very much *possible* that this is a hardware issue you'll have to seek to mitigate.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#12 2024-12-04 15:15:39

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

We won't know what's going on until you post a complet journal covering the incident, experiment w/ the holdoff timeout or monitor events w/ acpid, but it is very much *possible* that this is a hardware issue you'll have to seek to mitigate.

The problem is often hard to detect. As soon as it is again. I will attach the acpid output. Thank you

Offline

#13 2024-12-04 15:15:58

pvtvega
Member
Registered: 2024-11-25
Posts: 90

Re: [SOLVED] The laptop itself suspends

We can only speculate because you haven't provided the relevant logs. Walk us through the sequencing of this power issue:

1) If the laptop begins in an open, powered on, unsuspended state, and you close the lid, then re-open it, does it reliably enter a "sleep loop"?
2) Does suspending the system using any other method than closing the lid result in the same sleep loop?
3) If you change the #HoldoffTimeoutSec parameter, does the sleep loop frequency change accordingly? (I suspect that yes it will)

A simple workaround would just be to disable the lid switch and then rely on manually suspending the system.

Offline

#14 2024-12-04 17:59:38

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

Here is the output of journal -b on this error http://0x0.st/X7pn.txt

Last edited by kushiko (2024-12-04 18:00:11)

Offline

#15 2024-12-05 05:43:13

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

This is all from the lid:

дек 05 00:47:48 cyberlair kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/PNP0C09:00/PNP0C0D:00/input/input0
дек 05 00:47:48 cyberlair kernel: ACPI: button: Lid Switch [LID0]
дек 05 00:47:50 cyberlair systemd-logind[553]: Watching system buttons on /dev/input/event0 (Lid Switch)
дек 05 00:47:50 cyberlair tor[577]: Configuration was valid
дек 05 00:51:21 cyberlair systemd-logind[553]: Lid closed.
дек 05 00:51:21 cyberlair root[5908]: LID closed

What's 

cat /proc/acpi/button/lid/LID0/state

before initially closing the lid and then after opening it and waking the notebook?

This is interesting:

дек 05 00:47:50 cyberlair acpid[551]: starting up with netlink and the input layer
дек 05 00:47:50 cyberlair acpid[551]: 1 rule loaded
дек 05 00:47:50 cyberlair acpid[551]: waiting for events: event logging is off
дек 05 00:47:50 cyberlair acpid[551]: client connected from 596[0:0]
дек 05 00:47:50 cyberlair acpid[551]: 1 client rule loaded
дек 05 00:47:58 cyberlair acpid[551]: client 596[0:0] has disconnected
дек 05 00:54:40 cyberlair sudo[6325]: code_wizard : TTY=pts/1 ; PWD=/home/code_wizard ; USER=root ; COMMAND=/usr/bin/systemctl enable acpid
дек 05 00:54:44 cyberlair sudo[6462]: code_wizard : TTY=pts/1 ; PWD=/home/code_wizard ; USER=root ; COMMAND=/usr/bin/systemctl start acpid

You're trying to start/enable but acpid is already running - did you just recently install and enable it or does its existence predate the wakeup problem?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#16 2024-12-05 06:56:10

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

This is all from the lid:

дек 05 00:47:48 cyberlair kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/PNP0C09:00/PNP0C0D:00/input/input0
дек 05 00:47:48 cyberlair kernel: ACPI: button: Lid Switch [LID0]
дек 05 00:47:50 cyberlair systemd-logind[553]: Watching system buttons on /dev/input/event0 (Lid Switch)
дек 05 00:47:50 cyberlair tor[577]: Configuration was valid
дек 05 00:51:21 cyberlair systemd-logind[553]: Lid closed.
дек 05 00:51:21 cyberlair root[5908]: LID closed

What's 

cat /proc/acpi/button/lid/LID0/state

before initially closing the lid and then after opening it and waking the notebook?

This is interesting:

дек 05 00:47:50 cyberlair acpid[551]: starting up with netlink and the input layer
дек 05 00:47:50 cyberlair acpid[551]: 1 rule loaded
дек 05 00:47:50 cyberlair acpid[551]: waiting for events: event logging is off
дек 05 00:47:50 cyberlair acpid[551]: client connected from 596[0:0]
дек 05 00:47:50 cyberlair acpid[551]: 1 client rule loaded
дек 05 00:47:58 cyberlair acpid[551]: client 596[0:0] has disconnected
дек 05 00:54:40 cyberlair sudo[6325]: code_wizard : TTY=pts/1 ; PWD=/home/code_wizard ; USER=root ; COMMAND=/usr/bin/systemctl enable acpid
дек 05 00:54:44 cyberlair sudo[6462]: code_wizard : TTY=pts/1 ; PWD=/home/code_wizard ; USER=root ; COMMAND=/usr/bin/systemctl start acpid

You're trying to start/enable but acpid is already running - did you just recently install and enable it or does its existence predate the wakeup problem?

Yes. I found that when cat /proc/acpi/button/lid/LID0/state fails, it outputs state: closed

Last edited by kushiko (2024-12-05 06:56:39)

Offline

#17 2024-12-05 06:58:07

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

I also noticed that with this error, if I close the lid again and open it, the problem goes away. Maybe it's the hardware itself?

Offline

#18 2024-12-05 07:09:58

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

Please avoid bloating the thread with full quotes.

I also noticed that with this error, if I close the lid again and open it, the problem goes away.

If this is deterministic, the state change may just fail to get registered.
Please address the acpid condition - if you've been using acpid before you likely would have wanted to disable the logind lid handling - if you just installed acpid now for diagnostics, it's probably not relevant.

How does the lid behave on a different kernel and sw stack, eg. https://grml.org ?

https://docs.kernel.org/firmware-guide/ … i-lid.html
Does "button.lid_init_state=open" help?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#19 2024-12-05 07:43:15

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

Does "button.lid_init_state=open" help?

Where to specify button.lid_init_state=open?

Offline

#20 2024-12-05 07:44:01

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

https://wiki.archlinux.org/title/Kernel_parameters

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#21 2024-12-05 08:09:04

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

Specifying button.lid_init_state=open helped. Even if /proc/acpi/button/lid/LID0/state is close, suspend is still not activated. But in journalctl -f there is a line `The lid device is not compliant to SW_LID`.

Offline

#22 2024-12-05 08:15:32

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

That's ok, does closing the lid still trigger the suspend?
And does it (still?) act as wakeup trigger?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#23 2024-12-05 08:53:27

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

That's ok, does closing the lid still trigger the suspend?
And does it (still?) act as wakeup trigger?

Everything seems to be working perfectly now. The only thing that confused me was the LID log. Is that normal?

Offline

#24 2024-12-05 11:35:00

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: [SOLVED] The laptop itself suspends

I suppose it's a direct consequence of overriding the button behavior.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#25 2024-12-08 14:16:12

kushiko
Member
Registered: 2024-12-03
Posts: 27

Re: [SOLVED] The laptop itself suspends

seth wrote:

I suppose it's a direct consequence of overriding the button behavior.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

The only thing that breaks after opening the lid is bluetooth, but I think that's for a separate thread that's already been discussed - https://bbs.archlinux.org/viewtopic.php?id=301519

Offline

Pages: 1

Board footer

Powered by FluxBB