You are not logged in.
Pages: 1
I performed a system update today and computer (Thinkpad t480s) started to randomly suspend. This issue has occurred periodically before, but after the kernel update, the suspends happen every one to two minutes. To save my sanity I masked sleep.target and suspend.target via systemctl to prevent this from happening, but ideally, I'd prefer to have proper sleep behavior. I've attached part of my jounralctl when the incident occurred.
1 Mar 05 08:23:44 thinkpad kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
2 Mar 05 08:23:44 thinkpad kernel: OOM killer disabled.
3 Mar 05 08:23:44 thinkpad kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
4 Mar 05 08:23:44 thinkpad kernel: printk: Suspending console(s) (use no_console_suspend to debug)
5 Mar 05 08:23:44 thinkpad kernel: e1000e: EEE TX LPI TIMER: 00000011
6 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: interrupt blocked
7 Mar 05 08:23:44 thinkpad kernel: ACPI: PM: Preparing to enter system sleep state S3
8 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: event blocked
9 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: EC stopped
10 Mar 05 08:23:44 thinkpad kernel: ACPI: PM: Saving platform NVS memory
11 Mar 05 08:23:44 thinkpad kernel: Disabling non-boot CPUs ...
12 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 1 is now offline
13 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 2 is now offline
14 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 3 is now offline
15 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 4 is now offline
16 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 5 is now offline
17 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 6 is now offline
18 Mar 05 08:23:44 thinkpad kernel: smpboot: CPU 7 is now offline
19 Mar 05 08:23:44 thinkpad kernel: ACPI: PM: Low-level resume complete
20 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: EC started
21 Mar 05 08:23:44 thinkpad kernel: ACPI: PM: Restoring platform NVS memory
22 Mar 05 08:23:44 thinkpad kernel: Enabling non-boot CPUs ...
23 Mar 05 08:23:44 thinkpad kernel: x86: Booting SMP configuration:
24 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
25 Mar 05 08:23:44 thinkpad kernel: CPU1 is up
26 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
27 Mar 05 08:23:44 thinkpad kernel: CPU2 is up
28 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
29 Mar 05 08:23:44 thinkpad kernel: CPU3 is up
30 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
31 Mar 05 08:23:44 thinkpad kernel: CPU4 is up
32 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
33 Mar 05 08:23:44 thinkpad kernel: CPU5 is up
34 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
35 Mar 05 08:23:44 thinkpad kernel: CPU6 is up
36 Mar 05 08:23:44 thinkpad kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
37 Mar 05 08:23:44 thinkpad kernel: CPU7 is up
38 Mar 05 08:23:44 thinkpad kernel: ACPI: PM: Waking up from system sleep state S3
39 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: interrupt unblocked
40 Mar 05 08:23:44 thinkpad kernel: ACPI: EC: event unblocked
41 Mar 05 08:23:44 thinkpad kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
42 Mar 05 08:23:44 thinkpad kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate itOffline
How many parallel windows installations are there?
Offline
None; only one installation of Arch is installed on my system. I'm using grub as well.
Last edited by tawkins (2022-03-05 14:06:10)
Offline
Meh, was worth a shot.
Please post a complete journal, maybe the lid is misfiring?
What if you mute the triggers in /etc/systemd/logind.conf ? (Don't forget to "systemctl restart systemd-logind")
Offline
Based on the journal and muting lidswitch in logind, I think the lid is misfiring. How can I fix that?
Offline
Start with a screwdriver?
Depending on how the lid switch is constructed and what the problem is, this can be hard to impossible to fix.
Offline
How can I disable the lid switch via software? My screen still turns off when I shut it
Offline
Based on … muting lidswitch in logind
??
Offline
This is what I have set, but my lid switch is still functioning
# 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 by creating "drop-ins" in
# the logind.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# 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
HandlePowerKey=ignore
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
HandleLidSwitchDocked=ignore
#HandleRebootKey=reboot
#HandleRebootKeyLongPress=poweroff
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#RebootKeyIgnoreInhibited=no
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RuntimeDirectoryInodes=400kOffline
Did you restart logind? (In doubt, reboot)
That being said, the DPMS likely isn't controlled by logind, but the problem is "random" ACPI behavior, not the display powering off (let alone when closing th lid) is it?
Offline
I rebooted the system, but the screen still randomly turns off and turns off when I close the lid. Journalctl is still displaying that it is because of a lid close. Can I disable sleep behavior with ACPI?
Offline
I assume there is a massuve language barrier.
Is this about the screen turning off or the system suspending and/or sleeping?
Also, how is this "random" if it's the consequence of you closing the lid??
Please post the complete system journal after such incident, eg.
sudo journalctl -b -1 | curl -F 'f:1=<-' ix.iofor the previous boot (in case of a restart) or
sudo journalctl -b | curl -F 'f:1=<-' ix.iofor the current boot.
Offline
Pages: 1