System waking up immediately on suspend

aleksejunas · 19 March 2023 07:54

Problems with suspend. Hoping someone can help me. Messed a little around with powertop, could that have made suspend stop working?
Output from sudo systemctl enable systemd-suspend.service

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

mars 19 07:49:03 yogi-penguin systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit systemd-suspend.service has begun execution.
░░ 
░░ The job identifier is 3497.
mars 19 07:49:03 yogi-penguin systemd-sleep[3397]: Entering sleep state 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The system has now entered the suspend sleep state.
mars 19 07:49:43 yogi-penguin systemd-sleep[3397]: Failed to put system to sleep. System resumed again: Device or resource busy
░░ Subject: System sleep state suspend left
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The system has now left the suspend sleep state.
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit systemd-suspend.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
mars 19 07:49:44 yogi-penguin systemd[1]: Failed to start System Suspend.
░░ Subject: A start job for unit systemd-suspend.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit systemd-suspend.service has finished with a failure.
░░ 
░░ The job identifier is 3497 and the job result is failed.
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 2.229s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit systemd-suspend.service completed and consumed the indicated resources.
mars 19 08:02:11 yogi-penguin systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit systemd-suspend.service has begun execution.
░░ 
░░ The job identifier is 4103.
mars 19 08:02:11 yogi-penguin systemd-sleep[5632]: Entering sleep state 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The system has now entered the suspend sleep state.
mars 19 08:02:51 yogi-penguin systemd-sleep[5632]: Failed to put system to sleep. System resumed again: Device or resource busy
░░ Subject: System sleep state suspend left
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The system has now left the suspend sleep state.
mars 19 08:02:51 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit systemd-suspend.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mars 19 08:02:51 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
mars 19 08:02:51 yogi-penguin systemd[1]: Failed to start System Suspend.

xabbu · 19 March 2023 07:59

Maybe explain what you want to do or what your real problem is.
Because you can’t enable the systemd-suspend.service and this is a good thing. “enable” mans start at boot, so it would mean that your system immediately suspend after boot and after wake up form suspend it would suspend immediately again. Which would make your system unusable.

Mirdarthos · 19 March 2023 08:01

The reason why it doesn’t have an [Install] section is, AFAIK because it has to be started manually.

Edit:

I have never even used mine, so it’s at his default, and I don’t have an [Install] section, either:

$ systemctl cat systemd-suspend.service
# /usr/lib/systemd/system/systemd-suspend.service
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  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.

[Unit]
Description=System Suspend
Documentation=man:systemd-suspend.service(8)
DefaultDependencies=no
Requires=sleep.target
After=sleep.target

[Service]
Type=oneshot
ExecStart=/usr/lib/systemd/systemd-sleep suspend

aleksejunas · 19 March 2023 09:21

I just need suspend working again. Have no idea what happened/I did for this to happen. Any log output I can supply that can give some info to solve this problem. Thank you.

Mirdarthos · 19 March 2023 09:28

To help you, we need to know what’s wrong, and we don’t. We’ve only reesponded to your initial post, we don’t know what’s the matter, what happens. I suspect this is an XY problem right here, and we need more, detailed information from you, as our crystal ball comes up empty.

Edit:

See here:

aleksejunas · 19 March 2023 09:31

Sorry for not being explicit enough. The computer just won’t suspend. It tries, but just wakes up again. I have no idea what’s the cause for it. It used to work, but suddenly stopped working. Hope this clarifies things

Mirdarthos · 19 March 2023 09:40

Please provide the output of:

journalctl --boot=-1 --grep="suspend"

Where:

--boot=-1 is the last boot you had the problem on. Feel free to adjust this as required, -1 for the previous boot, -2 for the one before that, and so on and so forth;
--grep="suspend" searches the output for any and all mentions of “suspend”.

aleksejunas · 19 March 2023 09:42

mars 19 08:35:48 yogi-penguin kernel: Low-power S0 idle used by default for system suspend
mars 19 08:35:48 yogi-penguin kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
mars 19 08:36:37 yogi-penguin dbus-daemon[879]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.129' (uid=0 pid=6>
mars 19 08:36:41 yogi-penguin dbus-daemon[879]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1>
mars 19 08:36:41 yogi-penguin sudo[6133]:     rolf : TTY=pts/0 ; PWD=/home/rolf ; USER=root ; COMMAND=/usr/bin/systemctl status systemd-suspend.service
mars 19 08:36:54 yogi-penguin systemd-logind[883]: The system will suspend now!
mars 19 08:36:54 yogi-penguin ModemManager[913]: <info>  [sleep-monitor-systemd] system is about to suspend
mars 19 08:36:56 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 08:36:56 yogi-penguin systemd-sleep[7451]: Entering sleep state 'suspend'...
mars 19 08:36:56 yogi-penguin kernel: PM: suspend entry (s2idle)
mars 19 08:37:16 yogi-penguin kernel: PM: suspend exit
mars 19 08:37:16 yogi-penguin kernel: PM: suspend entry (s2idle)
mars 19 08:37:36 yogi-penguin kernel: PM: suspend exit
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 08:37:36 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 08:37:36 yogi-penguin systemd[1]: Dependency failed for Suspend.
mars 19 08:37:36 yogi-penguin audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/>
mars 19 08:37:36 yogi-penguin systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 2.548s CPU time.
mars 19 08:37:36 yogi-penguin kernel: audit: type=1130 audit(1679211456.625:201): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-suspend comm="sys>
mars 19 08:38:29 yogi-penguin dbus-daemon[879]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1>
mars 19 08:38:29 yogi-penguin sudo[13339]:     rolf : TTY=pts/0 ; PWD=/home/rolf ; USER=root ; COMMAND=/usr/bin/journalctl system_suspend.service
mars 19 08:38:38 yogi-penguin dbus-daemon[879]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1>
mars 19 08:38:38 yogi-penguin sudo[13914]:     rolf : TTY=pts/0 ; PWD=/home/rolf ; USER=root ; COMMAND=/usr/bin/journalctl system_suspend.service
mars 19 08:38:49 yogi-penguin dbus-daemon[879]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1>
mars 19 08:38:49 yogi-penguin sudo[14578]:     rolf : TTY=pts/0 ; PWD=/home/rolf ; USER=root ; COMMAND=/usr/bin/journalctl system_suspend.service

Mirdarthos · 19 March 2023 09:45

Please provide the output for:

journalctl --unit=systemd-suspend.service --no-pager --boot=-1

Where:

--boot=-1 is the last boot you had the problem on. Feel free to adjust this as required, -1 for the previous boot, -2 for the one before that, and so on and so forth;
--no-pager formats the output to be more suitable for use here; and
--unit=systemd-suspend.service limits the output to messages from the, you guessed it, suspend service.

aleksejunas · 19 March 2023 09:51

Here you go It’s enough with the last couple of days?

mars 18 21:07:50 yogi-penguin systemd-sleep[429597]: Entering sleep state 'suspend'...
mars 18 21:08:30 yogi-penguin systemd-sleep[429597]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 18 21:08:30 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 18 21:08:30 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 18 21:08:30 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 18 21:08:30 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 5.551s CPU time.
mars 18 21:08:30 yogi-penguin systemd[1]: Starting System Suspend...
mars 18 21:08:30 yogi-penguin systemd-sleep[429800]: Entering sleep state 'suspend'...
mars 18 21:09:11 yogi-penguin systemd-sleep[429800]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 18 21:09:11 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 18 21:09:11 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 18 21:09:11 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 18 21:09:11 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 5.568s CPU time.
mars 18 21:09:11 yogi-penguin systemd[1]: Starting System Suspend...
mars 18 21:09:11 yogi-penguin systemd-sleep[429995]: Entering sleep state 'suspend'...
mars 18 21:09:51 yogi-penguin systemd-sleep[429995]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 18 21:09:52 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 18 21:09:52 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 18 21:09:52 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 18 21:09:52 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 5.914s CPU time.
mars 18 21:09:52 yogi-penguin systemd[1]: Starting System Suspend...
mars 18 21:09:52 yogi-penguin systemd-sleep[430195]: Entering sleep state 'suspend'...
mars 18 21:10:32 yogi-penguin systemd-sleep[430195]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 18 21:10:32 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 18 21:10:32 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 18 21:10:32 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 18 21:10:32 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 5.867s CPU time.
mars 18 21:28:30 yogi-penguin systemd[1]: Starting System Suspend...
mars 18 21:28:30 yogi-penguin systemd-sleep[435474]: Entering sleep state 'suspend'...
mars 18 21:29:10 yogi-penguin systemd-sleep[435474]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 18 21:29:10 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 18 21:29:10 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 18 21:29:10 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 18 21:29:10 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 6.823s CPU time.
-- Boot 92de826105bb49c195edc5b0d39d92bb --
mars 19 07:49:03 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 07:49:03 yogi-penguin systemd-sleep[3397]: Entering sleep state 'suspend'...
mars 19 07:49:43 yogi-penguin systemd-sleep[3397]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 07:49:44 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 07:49:44 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 2.229s CPU time.
mars 19 08:02:11 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 08:02:11 yogi-penguin systemd-sleep[5632]: Entering sleep state 'suspend'...
mars 19 08:02:51 yogi-penguin systemd-sleep[5632]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 08:02:51 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 08:02:51 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 08:02:51 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 08:02:51 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 3.362s CPU time.
-- Boot 7211f91c8d7f47a4896c14be02d2e502 --
mars 19 08:36:56 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 08:36:56 yogi-penguin systemd-sleep[7451]: Entering sleep state 'suspend'...
mars 19 08:37:36 yogi-penguin systemd-sleep[7451]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 08:37:36 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 08:37:36 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 2.548s CPU time.
-- Boot c7b1ec13fc744702b1c5bbd8cbf3c4b3 --
mars 19 08:40:36 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 08:40:36 yogi-penguin systemd-sleep[4702]: Entering sleep state 'suspend'...
mars 19 08:41:16 yogi-penguin systemd-sleep[4702]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 08:41:16 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 08:41:16 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 08:41:16 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 08:41:16 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 2.159s CPU time.
mars 19 09:23:20 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 09:23:20 yogi-penguin systemd-sleep[161407]: Entering sleep state 'suspend'...
mars 19 09:24:00 yogi-penguin systemd-sleep[161407]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 09:24:00 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 09:24:00 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 09:24:00 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 09:24:00 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 3.038s CPU time.
mars 19 09:44:01 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 09:44:01 yogi-penguin systemd-sleep[164419]: Entering sleep state 'suspend'...
mars 19 09:44:41 yogi-penguin systemd-sleep[164419]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 09:44:41 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 09:44:41 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 09:44:41 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 09:44:41 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 3.058s CPU time.
mars 19 10:04:42 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 10:04:42 yogi-penguin systemd-sleep[166143]: Entering sleep state 'suspend'...
mars 19 10:05:22 yogi-penguin systemd-sleep[166143]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 10:05:22 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 10:05:22 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 10:05:22 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 10:05:22 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 3.179s CPU time.
mars 19 10:36:05 yogi-penguin systemd[1]: Starting System Suspend...
mars 19 10:36:05 yogi-penguin systemd-sleep[169945]: Entering sleep state 'suspend'...
mars 19 10:36:45 yogi-penguin systemd-sleep[169945]: Failed to put system to sleep. System resumed again: Device or resource busy
mars 19 10:36:45 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 19 10:36:45 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 19 10:36:45 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 19 10:36:45 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 3.655s CPU time.

Mirdarthos · 19 March 2023 09:58

I guess so, yes!

I see multiple of these lines, but they all end with:

And it doesn’t really tell us anything about why it happens. So let’s see if we can find out. Please run the following and provide any output response:

sudo systemctl start systemd-suspend.service

Mirdarthos · 19 March 2023 10:36

Because of this

I’ve got a feeling it’s related to this:

aleksejunas · 20 March 2023 08:21

Suspend works great in windows and in Live Ubuntu and it used to work here to. So it has nothing to do with bios settings. My output of journalctl -b -g suspend gives this output

mars 20 08:33:33 yogi-penguin kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
mars 20 09:09:11 yogi-penguin systemd-logind[899]: The system will suspend now!
mars 20 09:09:11 yogi-penguin ModemManager[942]: <info>  [sleep-monitor-systemd] system is about to suspend
mars 20 09:09:12 yogi-penguin systemd[1]: Starting System Suspend...
mars 20 09:09:12 yogi-penguin systemd-sleep[9762]: Entering sleep state 'suspend'...
mars 20 09:09:12 yogi-penguin kernel: PM: suspend entry (s2idle)
mars 20 09:09:32 yogi-penguin kernel: PM: suspend exit
mars 20 09:09:32 yogi-penguin kernel: PM: suspend entry (s2idle)
mars 20 09:09:52 yogi-penguin kernel: PM: suspend exit
mars 20 09:09:53 yogi-penguin systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
mars 20 09:09:53 yogi-penguin systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
mars 20 09:09:53 yogi-penguin systemd[1]: Failed to start System Suspend.
mars 20 09:09:53 yogi-penguin audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mars 20 09:09:53 yogi-penguin systemd[1]: Dependency failed for Suspend.
mars 20 09:09:53 yogi-penguin systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
mars 20 09:09:53 yogi-penguin systemd[1]: systemd-suspend.service: Consumed 4.039s CPU time.
mars 20 09:09:53 yogi-penguin kernel: audit: type=1130 audit(1679299793.112:199): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'```

Mirdarthos · 20 March 2023 08:25

See my previous reply:

Unknown. ¯\_(ツ)_/¯:

Because of this
aleksejunas:
mars 19 08:37:16 yogi-penguin kernel: PM: suspend entry (s2idle)
I’ve got a feeling it’s related to this:

Welcome back to the forum +1 Please see same advice as:

megavolt · 20 March 2023 08:57

Please verify:

cat /sys/power/mem_sleep

cat /proc/acpi/wakeup

If deep is available, then add this to the kernel parameter: mem_sleep_default=deep.

Sidenote: s2idle is a suspend software mode. Same as what Android Smartphones uses to sleep or standby and wake up right away.

aleksejunas · 20 March 2023 09:23

You mean if deep is available in /sys/power/mem_sleep?

aleksejunas · 20 March 2023 09:36

There’s no deep available. Is it as easy as adding it?

megavolt · 20 March 2023 09:44

No. That means that deep is not available, so was not detected by the kernel. Usually the UEFI/BIOS reveals that to the kernel. It could be now the kernel or the UEFI/BIOS. If Ubuntu works, then could be probably the kernel. Or Ubuntu just set deep to default, also even if it was not detected. Most UEFI’s are just made for Windows, therefore you can try to adjust the OSI and mimic a Windows of a specific version to the BIOS/UEFI.

Anyway, you could try just adding it, would be worth a try.

aleksejunas · 20 March 2023 10:08

Thanks, I’ll give it a try

aleksejunas · 20 March 2023 11:16

Sadly it did not work