2:25 a.m.
When I try suspend with "systemctl suspend" my notebook Fedora 36
sometime do not suspend with "PM: Some devices failed to suspend, or
early wake event detected" error.
Someone can help me to resolve this issue?
Many thanks
Dario
#----------------------------
set 14 00:41:26 dodo.home.solinos.it kernel: PM: suspend entry (s2idle)
set 14 00:41:26 dodo.home.solinos.it kernel: Filesystems sync: 0.006 seconds
set 14 00:41:28 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed
0.005 seconds) done.
set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer disabled.
set 14 00:41:28 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ...
(elapsed 0.002 seconds) done.
set 14 00:41:28 dodo.home.solinos.it kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend():
hcd_pci_suspend+0x0/0x30 returns -16
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM:
dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend
async: error -16
set 14 00:41:28 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early
wake event detected
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no
scrubber binary!
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4
using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl
300)
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number
6 using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number
8 using xhci_hcd
set 14 00:41:28 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds
set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer enabled.
set 14 00:41:28 dodo.home.solinos.it kernel: Restarting tasks ... done.
set 14 00:41:28 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05
occurred
set 14 00:41:28 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out
thermal zone (-61)
set 14 00:41:29 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event
0x0
set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend exit
set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend entry (s2idle)
set 14 00:41:29 dodo.home.solinos.it kernel: Filesystems sync: 0.002 seconds
set 14 00:41:31 dodo.home.solinos.it kernel: Freezing user space processes ... (elapsed
0.002 seconds) done.
set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer disabled.
set 14 00:41:31 dodo.home.solinos.it kernel: Freezing remaining freezable tasks ...
(elapsed 0.003 seconds) done.
set 14 00:41:31 dodo.home.solinos.it kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp
0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops
i915_hdcp_component_ops [i915])
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: pci_pm_suspend():
hcd_pci_suspend+0x0/0x30 returns -16
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM:
dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend
async: error -16
set 14 00:41:31 dodo.home.solinos.it kernel: PM: Some devices failed to suspend, or early
wake event detected
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: Refused to change power
state from D3hot to D0
set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0: fb: VPR locked, but no
scrubber binary!
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3: reset high-speed USB device number 4
using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: ata1: SATA link down (SStatus 4 SControl
300)
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.1: reset low-speed USB device number
6 using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.2: reset high-speed USB device number
8 using xhci_hcd
set 14 00:41:31 dodo.home.solinos.it kernel: PM: resume devices took 1.418 seconds
set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer enabled.
set 14 00:41:31 dodo.home.solinos.it kernel: Restarting tasks ...
set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp
0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops
i915_hdcp_component_ops [i915])
set 14 00:41:31 dodo.home.solinos.it kernel: done.
set 14 00:41:31 dodo.home.solinos.it gvfsd[219783]: PTP: reading event an error 0x05
occurred
set 14 00:41:31 dodo.home.solinos.it kernel: thermal thermal_zone9: failed to read out
thermal zone (-61)
set 14 00:41:31 dodo.home.solinos.it systemd-sleep[225719]: Failed to put system to sleep.
System resumed again: Device or resource busy
set 14 00:41:31 dodo.home.solinos.it kernel: PM: suspend exit
set 14 00:41:31 dodo.home.solinos.it bluetoothd[1739]: Controller resume with wake event
0x0
set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Main process
exited, code=exited, status=1/FAILURE
set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-suspend.service: Failed with
result 'exit-code'.
set 14 00:41:31 dodo.home.solinos.it systemd[1]: Failed to start systemd-suspend.service -
System Suspend.
set 14 00:41:31 dodo.home.solinos.it audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=failed'
set 14 00:41:31 dodo.home.solinos.it systemd[1]: Dependency failed for suspend.target -
Suspend.
set 14 00:41:31 dodo.home.solinos.it systemd[1]: suspend.target: Job suspend.target/start
failed with result 'dependency'.
set 14 00:41:31 dodo.home.solinos.it ModemManager[1836]: <info> [sleep-monitor]
system is resuming
set 14 00:41:31 dodo.home.solinos.it systemd-logind[1762]: Operation 'sleep'
finished.
--
Dario Lesca
(inviato dal mio Linux Fedora 36 Workstation)
10:31 a.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
On Wed, 14 Sep 2022 09:25:12 +0200
Dario Lesca <d.lesca(a)solinos.it> wrote:
When I try suspend with "systemctl suspend" my notebook
Fedora 36
sometime do not suspend with "PM: Some devices failed to suspend, or
early wake event detected" error.
Someone can help me to resolve this issue?
It looks like you have a usb drive attached, and it fails to suspend
because it is out of sync.
set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend
async: error -16
Someone else had this issue, and asked a question on stackexchange, and
got an answer.
https://unix.stackexchange.com/questions/690620/how-to-enable-sync-on-sus...
Summary: You have to either issue a sync before suspend, or turn on
autosync in the kernel before suspend. Details there.
1:30 p.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha scritto:
Summary: You have to either issue a sync before suspend, or turn on
autosync in the kernel before suspend.
Thanks stan, I will try one of proposed solution.
A little question: why is this not the default behavior?
if a user wants to suspend, the operating system should suspend.
Dario.
4:47 p.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
On Wed, 2022-09-14 at 20:30 +0200, Dario Lesca wrote:
Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha
scritto:
> Summary: You have to either issue a sync before suspend, or turn on
> autosync in the kernel before suspend.
Thanks stan, I will try one of proposed solution.
A little question: why is this not the default behavior?
Are you sure it isn't the default? On my system sync_on_suspend is set
to 1, and I'm 99.99% certain I didn't do that myself since I don't
recall ever hearing of the option before now.
poc
9:15 a.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
Il giorno mer, 14/09/2022 alle 22.47 +0100, Patrick O'Callaghan ha
scritto:
Are you sure it isn't the default?
Yes You're right.
On my system the flag is set to 1 by default:
[lesca@dodo ~]$ cat /sys/power/sync_on_suspend
1
And other flag is set to sync and suspend
[lesca@dodo ~]$ grep -i suspend /boot/config-$(uname -r)
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_PM_TEST_SUSPEND=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
CONFIG_CXL_SUSPEND=y
CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250
CONFIG_USB_AUTOSUSPEND_DELAY=2
But sometime the suspend action do not work, also if I run:
[lesca@dodo ~]$ sudo sh -c 'sync; sync; systemctl suspend'
I must unplug all USB, then suspend.
There are some other thinks I can do?
Many Thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 36 Workstation)
7:14 p.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
On Wed, 14 Sep 2022 20:30:11 +0200
Dario Lesca <d.lesca(a)solinos.it> wrote:
Il giorno mer, 14/09/2022 alle 08.31 -0700, stan via users ha
scritto:
> Summary: You have to either issue a sync before suspend, or turn on
> autosync in the kernel before suspend.
Thanks stan, I will try one of proposed solution.
A little question: why is this not the default behavior?
I don't know the answer. Apparently there were issues at some point
with this switch, so it was made optional. I don't even have the
sync_on_suspend file on my system, though that might be because I don't
use suspend. You could check in the /boot/config files what it is set at
for your system kernel by
grep -i suspend /boot/config* | less
I have
# CONFIG_SUSPEND is not set
CONFIG_USB_AUTOSUSPEND_DELAY=2
But my kernel is custom configured, so you should check your kernels.
7:08 a.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
On Wed, Sep 14, 2022 at 9:14 PM stan via users <
users(a)lists.fedoraproject.org> wrote:
grep -i suspend /boot/config* | less
I have
# CONFIG_SUSPEND is not set
CONFIG_USB_AUTOSUSPEND_DELAY=2
But my kernel is custom configured, so you should check your kernels.
Fresh install on an old iMac (late 2012?):
% grep -i suspend /boot/config* | less
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_ARCH_SUSPEND_POSSIBLE=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_SUSPEND=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_SUSPEND_FREEZER=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_PM_TEST_SUSPEND=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_OLD_SIGSUSPEND3=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_CXL_SUSPEND=y
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250
/boot/config-5.19.6-200.fc36.x86_64:CONFIG_USB_AUTOSUSPEND_DELAY=2
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_ARCH_SUSPEND_POSSIBLE=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_SUSPEND=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_SUSPEND_FREEZER=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_PM_TEST_SUSPEND=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_OLD_SIGSUSPEND3=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_CXL_SUSPEND=y
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250
/boot/config-5.19.7-200.fc36.x86_64:CONFIG_USB_AUTOSUSPEND_DELAY=2
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_ARCH_SUSPEND_POSSIBLE=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_SUSPEND=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_SUSPEND_FREEZER=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_PM_TEST_SUSPEND=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_OLD_SIGSUSPEND3=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_CXL_SUSPEND=y
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250
/boot/config-5.19.8-200.fc36.x86_64:CONFIG_USB_AUTOSUSPEND_DELAY=2
5:13 p.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
I have resolve this problem follow this Arch Linux howto:
https://wiki.archlinux.org/title/Power_management#Hybrid-sleep_on_suspend...
I have add these lines at the end of /etc/systemd/sleep.conf file
SuspendMode=suspend
SuspendState=disk
HibernateMode=suspend
HibernateState=disk
Now suspend work fine every time
Thanks
Dario
Il giorno mer, 14/09/2022 alle 09.25 +0200, Dario Lesca ha scritto:
> When I try suspend with "systemctl suspend" my notebook Fedora 36
> sometime do not suspend with "PM: Some devices failed to suspend, or
> early wake event detected" error.
>
> Someone can help me to resolve this issue?
>
> Many thanks
> Dario
>
> #----------------------------
> set 14 00:41:26 dodo.home.solinos.it kernel: PM: suspend entry
> (s2idle)
> set 14 00:41:26 dodo.home.solinos.it kernel: Filesystems sync: 0.006
> seconds
> set 14 00:41:28 dodo.home.solinos.it kernel: Freezing user space
> processes ... (elapsed 0.005 seconds) done.
> set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer disabled.
> set 14 00:41:28 dodo.home.solinos.it kernel: Freezing remaining
> freezable tasks ... (elapsed 0.002 seconds) done.
> set 14 00:41:28 dodo.home.solinos.it kernel: printk: Suspending
> console(s) (use no_console_suspend to debug)
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: failed to suspend async: error -16
> set 14 00:41:28 dodo.home.solinos.it kernel: PM: Some devices failed
> to suspend, or early wake event detected
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> fb: VPR locked, but no scrubber binary!
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3: reset high-
> speed USB device number 4 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: ata1: SATA link down
> (SStatus 4 SControl 300)
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.1: reset low-
> speed USB device number 6 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.2: reset high-
> speed USB device number 8 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: PM: resume devices took
> 1.418 seconds
> set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer enabled.
> set 14 00:41:28 dodo.home.solinos.it kernel: Restarting tasks ...
> done.
> set 14 00:41:28 dodo.home.solinos.it gvfsd[219783]: PTP: reading
> event an error 0x05 occurred
> set 14 00:41:28 dodo.home.solinos.it kernel: thermal thermal_zone9:
> failed to read out thermal zone (-61)
> set 14 00:41:29 dodo.home.solinos.it bluetoothd[1739]: Controller
> resume with wake event 0x0
> set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend exit
> set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend entry
> (s2idle)
> set 14 00:41:29 dodo.home.solinos.it kernel: Filesystems sync: 0.002
> seconds
> set 14 00:41:31 dodo.home.solinos.it kernel: Freezing user space
> processes ... (elapsed 0.002 seconds) done.
> set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer disabled.
> set 14 00:41:31 dodo.home.solinos.it kernel: Freezing remaining
> freezable tasks ... (elapsed 0.003 seconds) done.
> set 14 00:41:31 dodo.home.solinos.it kernel: printk: Suspending
> console(s) (use no_console_suspend to debug)
> set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-
> b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops
> i915_hdcp_component_ops [i915])
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd 0000:00:14.0:
> PM: failed to suspend async: error -16
> set 14 00:41:31 dodo.home.solinos.it kernel: PM: Some devices failed
> to suspend, or early wake event detected
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau 0000:01:00.0:
> fb: VPR locked, but no scrubber binary!
> set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3: reset high-
> speed USB device number 4 using xhci_hcd
> set 14 00:41:31 dodo.home.solinos.it kernel: ata1: SATA link down
> (SStatus 4 SControl 300)
> set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.1: reset low-
> speed USB device number 6 using xhci_hcd
> set 14 00:41:31 dodo.home.solinos.it kernel: usb 1-3.2: reset high-
> speed USB device number 8 using xhci_hcd
> set 14 00:41:31 dodo.home.solinos.it kernel: PM: resume devices took
> 1.418 seconds
> set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer enabled.
> set 14 00:41:31 dodo.home.solinos.it kernel: Restarting tasks ...
> set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp 0000:00:16.0-
> b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops
> i915_hdcp_component_ops [i915])
> set 14 00:41:31 dodo.home.solinos.it kernel: done.
> set 14 00:41:31 dodo.home.solinos.it gvfsd[219783]: PTP: reading
> event an error 0x05 occurred
> set 14 00:41:31 dodo.home.solinos.it kernel: thermal thermal_zone9:
> failed to read out thermal zone (-61)
> set 14 00:41:31 dodo.home.solinos.it systemd-sleep[225719]: Failed to
> put system to sleep. System resumed again: Device or resource busy
> set 14 00:41:31 dodo.home.solinos.it kernel: PM: suspend exit
> set 14 00:41:31 dodo.home.solinos.it bluetoothd[1739]: Controller
> resume with wake event 0x0
> set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-
> suspend.service: Main process exited, code=exited, status=1/FAILURE
> set 14 00:41:31 dodo.home.solinos.it systemd[1]: systemd-
> suspend.service: Failed with result 'exit-code'.
> set 14 00:41:31 dodo.home.solinos.it systemd[1]: Failed to start
> systemd-suspend.service - System Suspend.
> set 14 00:41:31 dodo.home.solinos.it audit[1]: SERVICE_START pid=1
> uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> msg='unit=systemd-suspend comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=failed'
> set 14 00:41:31 dodo.home.solinos.it systemd[1]: Dependency failed
> for suspend.target - Suspend.
> set 14 00:41:31 dodo.home.solinos.it systemd[1]: suspend.target: Job
> suspend.target/start failed with result 'dependency'.
> set 14 00:41:31 dodo.home.solinos.it ModemManager[1836]: <info>
> [sleep-monitor] system is resuming
> set 14 00:41:31 dodo.home.solinos.it systemd-logind[1762]: Operation
> 'sleep' finished.
>
> --
> Dario Lesca
> (inviato dal mio Linux Fedora 36 Workstation)
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
7:15 p.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
On Tue, Nov 1, 2022 at 6:14 PM Dario Lesca <d.lesca(a)solinos.it> wrote:
I have resolve this problem follow this Arch Linux howto:
https://wiki.archlinux.org/title/Power_management#Hybrid-sleep_on_suspend...
I have add these lines at the end of /etc/systemd/sleep.conf file
SuspendMode=suspend
SuspendState=disk
HibernateMode=suspend
HibernateState=disk
Huh, good to know.
Thanks for sharing this,
-srw
2:25 a.m.
New subject: Fedora 36: suspend failed with "PM: Some devices failed to
suspend, or early wake event detected"
I also had to stop and disable dnf-makecache.timer and all updates
functions
$ sudo systemctl disable --now dnf-makecache.timer
I run sometime manually dnf update, only when I plan to reboot my
notebook.
When dnf-makecache work, prevent suspend with result 'dependency'[1],
and suspend service don't wait for dnf-makecache to finish and then
suspend. Unless there is some setting that allows me to do this.
If I invoke suspend, I want the system to suspend sooner or later, not
that it fails and leaves my system on.
Dario
[1]
[root@dodo ~]# journalctl --no-hostname -S '2 weeks ago' --grep
'dnf-makecache|suspend'|grep 'nov 02 21:0'
nov 02 21:05:56 sudo[3155036]: lesca : TTY=pts/7 ; PWD=/home/lesca ; USER=root ;
COMMAND=/usr/bin/systemctl suspend
nov 02 21:05:56 ModemManager[1839]: <info> [sleep-monitor] system is about to
suspend
nov 02 21:05:56 systemd[1]: Starting systemd-suspend.service - System Suspend...
nov 02 21:05:56 systemd-sleep[3155096]: Entering sleep state 'suspend'...
nov 02 21:06:14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
nov 02 21:06:14 systemd[1]: Starting dnf-makecache.service - dnf makecache...
nov 02 21:06:14 systemd[1]: systemd-suspend.service: Main process exited, code=exited,
status=1/FAILURE
nov 02 21:06:14 systemd[1]: systemd-suspend.service: Failed with result
'exit-code'.
nov 02 21:06:14 systemd[1]: Failed to start systemd-suspend.service - System Suspend.
nov 02 21:06:14 systemd[1]: Dependency failed for suspend.target - Suspend.
nov 02 21:06:14 systemd[1]: suspend.target: Job suspend.target/start failed with result
'dependency'.
nov 02 21:06:14 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
nov 02 21:06:14 systemd[1]: systemd-suspend.service: Consumed 13.078s CPU time.
nov 02 21:06:15 systemd[1]: dnf-makecache.service: Deactivated successfully.
nov 02 21:06:15 systemd[1]: Finished dnf-makecache.service - dnf makecache.
nov 02 21:06:15 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov 02 21:06:15 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Il giorno lun, 07/11/2022 alle 20.15 -0500, Slade Watkins via users ha
scritto:
> On Tue, Nov 1, 2022 at 6:14 PM Dario Lesca <d.lesca(a)solinos.it>
> wrote:
> >
> > I have resolve this problem follow this Arch Linux howto:
> >
https://wiki.archlinux.org/title/Power_management#Hybrid-sleep_on_suspend...
> >
> > I have add these lines at the end of /etc/systemd/sleep.conf file
> > SuspendMode=suspend
> > SuspendState=disk
> > HibernateMode=suspend
> > HibernateState=disk
>
> Huh, good to know.
>
> Thanks for sharing this,
> -srw
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
534
days inactive
589
days old
9 comments
5 participants
participants (5)
-
Dario Lesca -
George N. White III -
Patrick O'Callaghan -
Slade Watkins -
stan