Hello everyone
I’m running Ubuntu on a KANO (Acer Spin 714) using MrChromebox firmware 2509.4. Each time that I try to suspend it, the screen flashes (trying to suspend) but wakes up again inmediately. Checking the logs I see
journalctl --grep=‘sleep|suspend|resume’ --no-pager --since=‘-1hour’
Jan 01 20:06:10 systemd-logind[1471]: The system will suspend now!
Jan 01 20:06:10 ModemManager[1795]: [sleep-monitor-systemd] system is about to suspend
Jan 01 20:06:10 ModemManager[1795]: [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 01 20:06:10 NetworkManager[1624]: [1767326770.3064] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jan 01 20:06:10 NetworkManager[1624]: [1767326770.3069] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 01 20:06:10 NetworkManager[1624]: [1767326770.3073] device (wlp0s20f3): state change: activated → deactivating (reason ‘sleeping’, managed-type: ‘full’)
Jan 01 20:06:10 NetworkManager[1624]: [1767326770.3862] device (wlp0s20f3): state change: deactivating → disconnected (reason ‘sleeping’, managed-type: ‘full’)
Jan 01 20:06:10 systemd-logind[1471]: Suspend key pressed short.
Jan 01 20:06:10 systemd[1]: Reached target sleep.target - Sleep.
Jan 01 20:06:10 systemd[1]: Starting systemd-suspend.service - System Suspend…
Jan 01 20:06:10 systemd-sleep[8790]: Performing sleep operation ‘suspend’…
Jan 01 20:06:10 kernel: PM: suspend entry (s2idle)
Jan 01 20:06:11 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 01 20:06:11 kernel: PM: Some devices failed to suspend, or early wake event detected
Jan 01 20:06:11 bluetoothd[1361]: Controller resume with wake event 0x0
Jan 01 20:06:11 PM: suspend exit
Jan 01 20:06:11 PM: suspend entry (s2idle)
Jan 01 20:06:11 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 01 20:06:11 kernel: PM: Some devices failed to suspend, or early wake event detected
Jan 01 20:06:11 systemd-sleep[8790]: Failed to put system to sleep. System resumed again: Device or resource busy
Jan 01 20:06:11 bluetoothd[1361]: Controller resume with wake event 0x0
Jan 01 20:06:11 kernel: PM: suspend exit
Jan 01 20:06:11 systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Jan 01 20:06:11 systemd[1]: systemd-suspend.service: Failed with result ‘exit-code’.
Jan 01 20:06:11 systemd[1]: Failed to start systemd-suspend.service - System Suspend.
Jan 01 20:06:11 systemd[1]: Dependency failed for suspend.target - Suspend.
Jan 01 20:06:11 systemd[1]: suspend.target: Job suspend.target/start failed with result ‘dependency’.
Jan 01 20:06:11 systemd-logind[1471]: Operation ‘suspend’ finished.
Jan 01 20:06:11 systemd[1]: Stopped target sleep.target - Sleep.
Jan 01 20:06:11 ModemManager[1795]: [sleep-monitor-systemd] system is resuming
Jan 01 20:06:11 NetworkManager[1624]: [1767326771.4351] manager: sleep: wake requested (sleeping: yes enabled: yes)
dmesg
[ 1984.685306] PM: suspend entry (s2idle)
[ 1984.687086] Filesystems sync: 0.001 seconds
[ 1984.702713] Freezing user space processes
[ 1984.704867] Freezing user space processes completed (elapsed 0.002 seconds)
[ 1984.704875] OOM killer disabled.
[ 1984.704878] Freezing remaining freezable tasks
[ 1984.706713] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 1984.706727] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1984.770627] PM: Some devices failed to suspend, or early wake event detected
[ 1984.783952] max98373 i2c-MX98373:00: Reset completed (retry:0)
[ 1984.784839] max98373 i2c-MX98373:01: Reset completed (retry:0)
[ 1984.968874] OOM killer enabled.
[ 1984.968880] Restarting tasks: Starting
[ 1984.970722] Restarting tasks: Done
[ 1984.970783] efivarfs: resyncing variable state
[ 1984.972339] efivarfs: finished resyncing variable state
[ 1984.974407] random: crng reseeded on system resumption
[ 1984.977310] PM: suspend exit
While the logs show some activity on Bluetooth and the Audio Chip during the suspend process, I am not sure if those are really the cause of the issue…
Sorry, my Linux skills are not great, it’s more of a hobby that a real structured skill… What would be the proper next steps to find out where the problem is? How (or where) can I check which device failed to suspend?
Thanks a lot for your guidance to debug this issue !!!