I know that this question is posted a few times already, but I tried many of the solutions there and they didn't work. If I start my Laptop (restart or fresh boot after being turned off) the WiFi works most of the time and I can connect to it without a problem. *Not always though* If I'm connected and close the lid or press the power button so that the laptop goes into suspend mode, after I open it up again, I can't connect to the internet. The available networks are shown, but all of them only have a 10% strength and nothing happens when I try to connect to them. If I deactivate and activate WiFi again (either by the switch in network-manager or by the F-Key on the keyboard), it shows WiFi as "not connected". I tried to restart network-manager after the suspension, but that didn't fix the problem. I know that this is not a lot of debugging information, but I'm not knowledgeable enough of Linux to be able to give you a more relevant one. But I'm happy to provide it, if you tell me what exactly. EDIT: After thinking about the problem a little bit more I also remembered the following: If I let the Laptop suspend by going idle and waiting for the 5 minutes it requires, I sometimes have WiFi after booting up again. It also happened recently, that I was playing in offline mode (because I had no WiFi) and after quite some time I could connect to the Internet again (I think about an hour, but I'm not exactly sure). I have seen this phenomenon very rarely and it only happened on a few occasions.

When I boot up my system (I'm using Ubuntu 20.04), the keyboard isn't detected. The only way to have it working is to suspend the system and wake it up back. Then the keyboard is fully functioning. I tried using different acpi_osi kernel parameters without success. The same happens with differents Live USB. The keyboard works in BIOS though. My laptop model is Clevo PB71DF2-G and I fresh installed Ubuntu on it. Everything else works as expected. Does anyone have a solution ?

I’ve installed antiX 19.3 recently on a 16-yro (or older), laptop. One issue I’ve been having is that the thing keeps going to sleep! Every 30-45 seconds or so, it goes into sleep mode; and comes back up on a keypress. This includes even the boot sequence: While running the init scripts for runlevel 5, this already happens once. It continues after my desktop environment (IceWM) has loaded. I've read this highly related question , and found a workaround: Completely disable ACPI and APM on the grub2 boot line for the kernel: acpi=off apm=off. But that’s not a good solution, because it is important for the laptop to go to sleep when unused; and you want fan speed control etc. Another suggestion there involve systemd facilities - but my distribution doesn't use systemd. What else can I do? Also, what could be the cause of this? Here's the repeating segment of my dmesg:

[Wed May 12 17:11:00 2021] VFS: busy inodes on changed media or resized disk sr0
[Wed May 12 17:11:26 2021] PM: suspend entry (deep)
[Wed May 12 17:11:26 2021] PM: Syncing filesystems ... done.
[Wed May 12 17:11:26 2021] Freezing user space processes ... (elapsed 0.001 seconds) done.
[Wed May 12 17:11:26 2021] OOM killer disabled.
[Wed May 12 17:11:26 2021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[Wed May 12 17:11:26 2021] Suspending console(s) (use no_console_suspend to debug)
[Wed May 12 17:11:26 2021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[Wed May 12 17:11:26 2021] sd 0:0:0:0: [sda] Stopping disk
[Wed May 12 17:11:28 2021] ACPI: EC: interrupt blocked
[Wed May 12 17:11:28 2021] ACPI: Preparing to enter system sleep state S3
[Wed May 12 17:11:28 2021] ACPI: EC: event blocked
[Wed May 12 17:11:28 2021] ACPI: EC: EC stopped
[Wed May 12 17:11:28 2021] PM: Saving platform NVS memory
[Wed May 12 17:11:28 2021] Disabling non-boot CPUs ...
[Wed May 12 17:11:28 2021] ACPI: Low-level resume complete
[Wed May 12 17:11:28 2021] ACPI: EC: EC started
[Wed May 12 17:11:28 2021] PM: Restoring platform NVS memory
[Wed May 12 17:11:28 2021] ACPI: Waking up from system sleep state S3
[Wed May 12 17:11:28 2021] ACPI: EC: interrupt unblocked
[Wed May 12 17:11:28 2021] usb usb2: root hub lost power or was reset
[Wed May 12 17:11:28 2021] usb usb3: root hub lost power or was reset
[Wed May 12 17:11:28 2021] usb usb4: root hub lost power or was reset
[Wed May 12 17:11:28 2021] 8139too 0000:01:00.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[Wed May 12 17:11:28 2021] sd 0:0:0:0: [sda] Starting disk
[Wed May 12 17:11:28 2021] ACPI: EC: event unblocked
[Wed May 12 17:11:28 2021] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:28 2021] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
[Wed May 12 17:11:29 2021] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[Wed May 12 17:11:29 2021] firewire_core 0000:01:02.0: rediscovered device fw0
[Wed May 12 17:11:30 2021] OOM killer enabled.
[Wed May 12 17:11:30 2021] Restarting tasks ... done.
[Wed May 12 17:11:30 2021] PM: suspend exit
[Wed May 12 17:11:35 2021] VFS: busy inodes on changed media or resized disk sr0
[Wed May 12 17:12:01 2021] PM: suspend entry (deep)

Notes: * I should mention that this did not happen with the Windows XP installation which the laptop used to have. * The laptop’s battery is almost dead, so I only run it with mains power plugged in. * I tried switching the kernel version from 4.9.something to 4.19.something (antix-packaged images); no effect. * Laptop info: Clevo M3CW, Pentium M 1.6GHz, 1 GB memory, 40GB HDD. Has a built-in CD which is giving me another kind of trouble that's probably unrelated.

I am currently running Zorin OS 12 (based on Ubuntu 16.04 LTS, I'm pretty sure it's an Ubuntu problem specifically but I never encountered it running stock Ubuntu), and when plugged in from boot it works perfectly. However, as soon as I remove external power, I lose the ability to suspend the computer. Any attempts to suspend the system cause the screen to turn back on within about 10-15 seconds. This continues to happen until I reboot. I have a couple theories on why this may be happening, though I don't know which it is or even if either of them is actually what is happening. 1. I forgot to assign swap space when installing. Prior to assigning new swap space, this was occurring every time I suspended, whether on A/C power or battery. I doubt it though, because I now have 10 GB of swap when my physical memory is only 8 GB, and it only happens after I remove power. 2. Sometimes, when this happens, after I reopen the computer, my Wi-Fi card stops functioning, but in a weird way. It fails to detect any networks, but I can specify a 'hidden' network (the network I had connected to previously which is not hidden) and it immediately repopulates the network list. 3. I am unable to install the Intel Graphics Update Software to install official Intel drivers for my display because, despite being available for Ubuntu 16.04 and my computer reporting its kernel version as #80-Ubuntu (the same as a server I have access to which I know is running Ubuntu 16.04 directly), the software believes I do not run a supported distro. This seems to be the most likely cause to me, though I have never had issues with Intel Integrated graphics on any Linux distro in the past.

Recently, I've freshly installed Debian 12 on new ASUS Vivobook 16 Laptop. Suspend function doesn't seem to work tho. Hitting Suspend button under power option leads to black screen with underscore sign in left upper corner. Keyboard lights remain ON. It stays this way until any button is hit. Laptop wakes up from suspension fine. Using pm-suspend gives a slightly different results. Screen goes to black, but it's still on. No underscore sign tho. no problem with waking up. I've found this entry in logs:

Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler: line 231: ((: 0x10de ==  : syntax error: operand expected (error token is "==  ")

But I'm not sure where to go from here. Any ideas how to solve this issue? Full pm-suspend log: https://pastebin.com/pnwyM5Jz

When trying to suspend my laptop (HP Elitebook X G1a) with systemctl suspend or closing the lid it turns off the screen and back on again a few times before giving up. I'm using NixOS with a 6.12.32 kernel, with Hyprland, but it also happens on TTY. Unloading the module with modprobe -r mt7925e enables the suspend to complete, but I'd rather see why it doesn't work by itself. Also have the latest bios updates for my laptop. Hardware probe says the chip "works" and is supported since 6.7 I also tried using 6.14 and 6.15, adding acpi kernel params I tried a lot of things, but I can't seem to find a solution. Thanks in advance! This is the output of journalctl -p err when trying to suspend Jul 03 16:44:00 barlow kernel: mt7925e 0000:c2:00.0: Message 00020007 (seq 1) timeout Jul 03 16:44:00 barlow kernel: mt7925e 0000:c2:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend [mt7925e] returns -110 Jul 03 16:44:00 barlow kernel: mt7925e 0000:c2:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -110 Jul 03 16:44:00 barlow kernel: mt7925e 0000:c2:00.0: PM: failed to suspend async: error -110 Jul 03 16:44:00 barlow kernel: PM: Some devices failed to suspend, or early wake event detected Jul 03 16:44:05 barlow kernel: mt7925e 0000:c2:00.0: Message 00020007 (seq 2) timeout Jul 03 16:44:05 barlow kernel: mt7925e 0000:c2:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend [mt7925e] returns -110 Jul 03 16:44:05 barlow kernel: mt7925e 0000:c2:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -110 Jul 03 16:44:05 barlow kernel: mt7925e 0000:c2:00.0: PM: failed to suspend async: error -110 Jul 03 16:44:05 barlow kernel: PM: Some devices failed to suspend, or early wake event detected Jul 03 16:44:05 barlow systemd-sleep: Failed to put system to sleep. System resumed again: Connection timed out Jul 03 16:44:05 barlow systemd: Failed to start System Suspend.

My system has 64GiB of memory. I noticed it usually uses about 20GiB for cache. I wonder if I do "suspend to disk", does the cached part get dumped to disk as well, or is it written to disk before the system is suspended to disk? I want to reduce the actual total used memory before suspending to disk so that the system can wake up faster. Thanks

On my Ubuntu 20.04 (problem persists since 16.04) Sony VAIO laptop if I close the lid, wait till the yellow led to blink and then turn the laptop on again, awakes everything but keyboard, which turns on it's backlight after first keypress but doesn't react to anything, so does the touchpad. So I get almost fully working system, but completely unusuable. My problem is that I don't even know where to search for problem origin. I don't know how the laptop power and keyboard management works in Ubuntu, not on systemd or SysV level, nor on kernel level. So, no logs for you, my friends, until you ask for any. =) How can I solve this very annoying issue please?

As most issues people have had, I can't wake my laptop from suspend or hibernate mode. The computer goes to the lock screen and then freezes up to the point where the mouse won't move, forcing me to do a hard reboot. If you're interested in my uname -a output, here it is: Linux Jason-PC 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Here is the update of inxi -G: Graphics: Card: NVIDIA GK107GLM [Quadro K1000M] X.Org: 1.13.3 drivers: (unloaded: fbdev,vesa) FAILED: nouveau Resolution: 1600x900@60.0hz GLX Renderer: Gallium 0.4 on NVE7 GLX Version: 3.0 Mesa 9.1.4 ---- The computer now allows me to log in, but Linux becomes all glitchy and unusable. Here are some suspicious lines of syslog: Oct 12 12:42:44 Jason-PC mdm: WARNING: failed to get file info for accountService pic file: Error when getting information for file '/var/lib/AccountsService/icons/jajmo': No such file or directory Oct 12 12:42:44 Jason-PC mdm: WARNING: failed to get file info for accountService pic file: Error when getting information for file '/home/jajmo/.face': No such file or directory Oct 12 12:42:44 Jason-PC mdm: GLib-GIO-CRITICAL: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed Oct 12 12:42:44 Jason-PC mdm: GLib-GIO-CRITICAL: g_file_info_get_attribute_uint64: assertion 'G_IS_FILE_INFO (info)' failed As well as: Oct 12 12:42:37 Jason-PC kernel: [ 28.436602] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro

I have a Lenovo Helix 2, which has busted suspend-to-RAM (S3) support. "Light sleep" mode (S0ix), however, works fine, as tested with echo freeze > /sys/power/state. I can bind the power button to use freeze instead of mem using acpid event handlers, but what I really want to do is get the desktop environment to handle this, since it can do things like "suspend after N minutes of user inactivity" that acpid can't. Unfortunately, the only options the KDE power manager gives me are "Do Nothing", "Lock Screen", "Suspend", "Hibernate", and "Power Off". It has a "run script" option, but that only applies when transitioning between power states -- e.g. I could have it run a script when going from AC to battery, or from battery to low battery, but not when on battery power and idle for 30 minutes. So, is there some way -- either as part of KDE configuration, or as a systemd or sysfs or kernel option -- to override things so that it will try to freeze instead of, or as an alternative to, suspending?

I am running Centos 7 and all I want to do is make my computer go to sleep immediately. There is a setting I have set to make my computer go to sleep but only after a certain amount of inactivity but when I leave work, I want to be able to make it go to sleep immediately right after instead of turning my computer off. I looked and found this link https://www.cyberciti.biz/faq/linux-command-to-suspend-hibernate-laptop-netbook-pc/ and I tried both commands sudo systemctl suspend and sudo systemctl hibernate and get the message A dependency job for suspend.target failed. See 'journalctl -xe' for details. I just want to be able to make my computer go to sleep so that I can pick up from where I left off the day before instead of turning off my computer everytime I leave from work.

The only way I can wake up my laptop (HP Elitebook 8460p) from suspend is by pressing the power button. Neither the built-in keyboard/mouse nor the external ones (connected via USB) wake the laptop up. Things I already tried: * Enabling the USB devices in /proc/acpi/wakeup. * Checking the bootlog to find out the /dev paths of the USB mouse/keyboard, then: udevadm info -a -p $(udevadm info -q path -n /dev/input/mouse2) I then checked for every device in the list using: cat /sys/devices/.../power/wakeup if it is possible to enable it, and if so, I do that. * I have enabled wake on USB in the BIOS. Here some outputs you might need: **$ uname -a** Linux oliarch 2.6.38-ARCH #1 SMP PREEMPT Tue May 10 08:05:04 CEST 2011 x86_64 Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz GenuineIntel GNU/Linux **\# lsusb** Bus 001 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Bus 003 Device 005: ID 03f0:231d Hewlett-Packard **\# lspci** 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 6 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.2 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 3 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.7 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 8 (rev b4) 00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 6 Series Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 23:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller (rev 30) 23:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30) 23:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30) 24:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34) 25:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) **\# cat /proc/acpi/wakeup** Device S-state Status Sysfs node LANC S0 *enabled pci:0000:00:19.0 EHC1 S3 *enabled pci:0000:00:1d.0 EHC2 S3 *enabled pci:0000:00:1a.0 PCIB S5 *disabled RP02 S4 *disabled pci:0000:00:1c.1 ECF0 S4 *disabled RP03 S4 *disabled pci:0000:00:1c.2 RP04 S5 *disabled pci:0000:00:1c.3 WNIC S5 *disabled pci:0000:24:00.0 RP08 S4 *disabled pci:0000:00:1c.7 HST1 S5 *disabled Any ideas?

Yocto System taking more time to resume from S3 sleep, it should take 2sec, but taking 12sec: Suspend entry: [ 244.086061] PM: suspend entry (deep) Low-level resume complete: [ 246.900251] Suspend exit: [ 247.970167] Display usable (login/dmesg): [ 257.556554] sshd or ACP logs visible Stage Time (sec) Suspend → Low-level resume ~2.81s Suspend → Suspend exit ~3.88s Suspend → Usable system ~13.5s How do I diagnose this and identify the part where it gets stuck for so long?

I am trying to run Ubuntu 18.04 on a laptop with an AMD A12 processor and Radeon R7 graphics. I am having nothing but problems and am very discouraged with Ubuntu though I used 12.04 for years without such problems. I have two problems that are maddening, and I will post them separately. The problems happen only on Gnome and Ubuntu on Xorg and do not happen on Wayland. However, I am told that it's best not to run Gnome on Wayland. This problem is that the computer sometimes doesn't wake up from suspend. Well, I think it does wake up because the optical drive spins and the hard drive ticks away, but I cannot login because the lock screen is a hash of colors or a distorted background without a place to login. I cannot even Ctrl-Alt-F1 to get to a prompt. All input is frozen. I am wondering if Xorg is configured correctly. I am running the Oilaf video driver which works well under Wayland so I don't know if there is a problem with Xorg and that driver.

system hang with G2/G3 NIC card after resuming from S3 suspend. But it works with G1 NIC & ethernet. What is the culprit here xhci_hcd 0000:03:00.3: Controller not ready at resume -19 xhci_hcd 0000:03:00.3: PCI post-resume error -19! xhci_hcd 0000:03:00.3: HC died; cleaning up xhci_hcd 0000:03:00.4: Controller not ready at resume -19 xhci_hcd 0000:03:00.4: PCI post-resume error -19! xhci_hcd 0000:03:00.4: HC died; cleaning up xhci_hcd 0000:03:00.3: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.4: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.3: PM: failed to resume async: error -19 xhci_hcd 0000:03:00.4: PM: failed to resume async: error -19

I need to remove Suspend / Restart / Power Off… menu from Gnome Shell & GDM. I’ve been trying using Settings, Gnome Tweaks, Dconf Editor, but nothing found AFAIK. Trying to enter the Polkit conf file gave the same results. polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.login1.power-off" || action.id == "org.freedesktop.login1.reboot" || action.id == "org.freedesktop.login1.hibernate" || action.id == "org.freedesktop.login1.suspend") { return polkit.Result.NO; } }); Any clue? Thank you, Regards

I have a Fedora Linux system under my desk at home. It runs the Workstation setup (with GNOME) even though it mostly is used headless. It is my file server (samba), mail server (dovecot, mailman) and webserver (apache, perl-cgi). But recently,I am using digiKam to manage my photo connection, and I do this from a GNOME session. When I upgraded to Fedora 40,

started shutting down (suspending) the system when idle, which of course prevented my server services from accepting connections. I fixed this with

mask suspend

and

mask sleep

. But recently, this is not enough: When I am logged in remotely by

, I will get interrupted every minute or so with

Broadcast message from root@cleo.beagle-ears.com (Mon 2025-04-14 15:07:31 PDT):

The system will suspend now!

How do I get rid of this?

I have a acer aspire 5750G laptop. I am running ubuntu 11.04. The uname -a reads the following: > Linux admin-Aspire-5750G 2.6.38-13-generic-pae #56-Ubuntu SMP Tue Feb 14 14:32:30 UTC 2012 i686 i686 i386 GNU/Linux Whenever the wakes up from suspend or hibernate, it shows a blank screen. Same thing happens when the lid is closed and opened later. What should I do to fix this? **Edit#1:** I have the pm-utils installed. I could suspend using pm-suspend. When I press any key to wake up, the machine wakes up but hangs. It does not respond to any keyboard or mouse keys after wake up. What could be wrong here?

I am working on an embedded Linux system (kernel-5.10.220). Now I am testing the suspend and resume in this system with a watchdog time as the wakeup source to wake system up from suspend. The watchdog interrupt comes in every 5 seconds, and the script calls sleep 10 to add 10 seconds delay between continous test. And there is NO RTC in system! Here is my testing script.

#!/bin/sh

trap ctrl_c INT

function ctrl_c()
{
    echo "Exiting"
    exit 0
}

count=0
sec=10

while [ true ]
do
    echo ">>>>>>>>>>> Testing suspend $count"
    echo mem > /sys/power/state
    echo ">>>>>>>>>> Testing suspend 0
>>>>>>>>>> Testing suspend 1
>>>>>>>>>> Testing suspend 2
>>>>>>>>>> Testing suspend 3
>>>>>>>>>> Testing suspend 4
>>>>>>>>>> Testing suspend 5
>>>>>>>>>> Testing suspend 6
<<<<<<<<<<< Resumed after suspend

Thu Jan  1 06:33:12 UTC 1970

From the output of date, the script did NOT delay 10 seconds between tests. The real interval of 10 seconds sleeping is about 2 or 3 seconds! So why sleep 10 did NOT sleep for 10 seconds in the suspend and resume testing?

I have a Linux system based on minimal Ubuntu 22.04 and kernel 6.5.3 that uses systemd as its init. Shortly after boot, something causes the system to suspend, which is undesirable, as there's no means to wake it. I suspect it's something to do with a USB-attached touch pad, because swapping for a different model of touch-pad fixes the symptom. Note that swapping for another of the same model still suspends, so it's not a failed peripheral; also the problem touch pad works find with a different model of motherboard, so it's clearly due to the combination of host and device. Also, this behaviour didn't occur with a previous installation based on Ubuntu 14.04 with Upstart as init. I have been able to access the system and run systemctl mask target.sleep; that provides an adequate work-around for the time being. But I'd like to understand and perhaps eliminate the root cause. **What tools are available to investigate why systemd is attempting to reach the "sleep" target?** I'm hoping there's something I can inspect on the running system (with target.sleep masked) to track down where the desire to sleep originates. If needed, I can systemctl unmask target.sleep (causing the system to suspend immediately) then inspect logs after powering down and rebooting. I'm happy to install extra packages or to recompile the kernel with extra options - I just don't know which ones I should be using.