With all recent updates of Byzantium, suspend seems to fail on my L5.
It tries to suspend and in a second or two the screen lights up again. And the cycle continues.
If I open the tweak app and Go to LIbrem5 and click on the suspend button, it blanks the screen for a moment (trying to suspend I guess) and in the next second the screen lights up again.
Does this happen to you? How can I debug/fix this? Something prohibits suspend…
Just checked now : suspend from the tweak app works for me (all recent Byzantium updates too).
Look with an editor into /var/log/syslog. A typical suspend wakeup should be look like this here: suspend at 08:33, wakeup at 09:10:
Mar 4 08:33:36 pureos systemd[1]: Starting Suspend...
Mar 4 08:33:36 pureos systemd-sleep[16659]: Suspending system...
Mar 4 08:33:36 pureos kernel: [88188.392665] PM: suspend entry (deep)
Mar 4 08:33:36 pureos kernel: [88188.445519] Filesystems sync: 0.052 seconds
Mar 4 09:10:14 pureos kernel: [88188.446312] Freezing user space processes
Mar 4 09:10:14 pureos kernel: [88188.450274] Freezing user space processes completed (elapsed 0.003 seconds)
Mar 4 09:10:14 pureos kernel: [88188.450299] OOM killer disabled.
journalctl gives (I left some messages around the bold part since I do not know if they matter).
Mar 04 18:32:38 pureos mmsdtng[676]: …/plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Mar 04 18:32:38 pureos mmsdtng[676]: …/src/service.c:mms_service_set_bearer_handler() service 0xaaaaef67bba0 handler 0xaaaabe585a20
Mar 04 18:32:38 pureos kernel: edt_ft5x06 2-0038: Unable to fetch data, error: -6
Mar 04 18:32:38 pureos gsd-xsettings[1008]: Failed to get current UI legacy scaling factor
Mar 04 18:32:38 pureos gsd-xsettings[1008]: Failed to get current UI legacy scaling factor
Mar 04 18:32:38 pureos gsd-color[982]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Mar 04 18:32:38 pureos ModemManager[599]: [modem0] state changed (disconnecting → registered)
Mar 04 18:32:38 pureos ModemManager[599]: [modem0/bearer1] connection #1 finished: duration 366s, tx: 373690 bytes, rx: 10635486 bytes
Mar 04 18:32:38 pureos mmsdtng[676]: …/plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 9 New State: 8, Reason: 1
Mar 04 18:32:38 pureos mmsdtng[676]: …/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 8
Mar 04 18:32:38 pureos mmsdtng[676]: …/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
Mar 04 18:32:38 pureos mmsdtng[676]: …/plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Mar 04 18:32:38 pureos mmsdtng[676]: …/src/service.c:mms_service_set_bearer_handler() service 0xaaaaef67bba0 handler 0xaaaabe585a20
Mar 04 18:32:38 pureos NetworkManager[486]: [1709569958.7514] modem[“cdc-wdm0”]: modem state changed, ‘disconnecting’ → ‘registered’ (reason: user-requested)
Mar 04 18:32:38 pureos NetworkManager[486]: [1709569958.7517] device (cdc-wdm0): state change: deactivating → disconnected (reason ‘sleeping’, sys-iface-state: ‘managed’)
Mar 04 18:32:38 pureos NetworkManager[486]: [1709569958.7623] device (cdc-wdm0): state change: disconnected → unmanaged (reason ‘sleeping’, sys-iface-state: ‘managed’)
Mar 04 18:32:38 pureos systemd[1]: Reached target Sleep.
Mar 04 18:32:38 pureos systemd[1]: Starting Suspend…
Mar 04 18:32:38 pureos systemd-sleep[1981]: Suspending system…
Mar 04 18:32:38 pureos kernel: PM: suspend entry (deep)
Mar 04 18:32:39 pureos kernel: Filesystems sync: 0.028 seconds
Mar 04 18:32:39 pureos kernel: Freezing user space processes
Mar 04 18:32:39 pureos kernel: Freezing user space processes completed (elapsed 0.009 seconds)
Mar 04 18:32:39 pureos kernel: OOM killer disabled.
Mar 04 18:32:39 pureos kernel: Freezing remaining freezable tasks
Mar 04 18:32:39 pureos kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Mar 04 18:32:39 pureos kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 04 18:32:39 pureos kernel: Disabling non-boot CPUs …
Mar 04 18:32:39 pureos kernel: psci: CPU1 killed (polled 0 ms)
Mar 04 18:32:39 pureos kernel: psci: CPU2 killed (polled 0 ms)
Mar 04 18:32:39 pureos kernel: psci: CPU3 killed (polled 4 ms)
Mar 04 18:32:39 pureos kernel: Enabling non-boot CPUs …
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU1
Mar 04 18:32:39 pureos kernel: GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
Mar 04 18:32:39 pureos kernel: CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU1 is up
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU2
Mar 04 18:32:39 pureos kernel: GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
Mar 04 18:32:39 pureos kernel: CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU2 is up
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU3
Mar 04 18:32:39 pureos kernel: GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
Mar 04 18:32:39 pureos kernel: CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU3 is up
Mar 04 18:32:39 pureos kernel: caam 30900000.crypto: registering rng-caam
Mar 04 18:32:39 pureos kernel: OOM killer enabled.
Mar 04 18:32:39 pureos kernel: Restarting tasks … done.
Mar 04 18:32:39 pureos kernel: random: crng reseeded on system resumption
Mar 04 18:32:39 pureos kernel: thermal thermal_zone3: failed to read out thermal zone (-61)
Mar 04 18:32:39 pureos kernel: PM: suspend exit
Mar 04 18:32:39 pureos systemd-sleep[1981]: System resumed.
Mar 04 18:32:39 pureos ModemManager[599]: [sleep-monitor] system is resuming
Mar 04 18:32:39 pureos systemd[1]: systemd-suspend.service: Succeeded.
Mar 04 18:32:39 pureos ModemManager[599]: [modem0] resume synchronization state (1/4): modem interface sync
Mar 04 18:32:39 pureos systemd[1]: Finished Suspend.
Mar 04 18:32:39 pureos ModemManager[599]: [modem0] resume synchronization state (2/4): 3GPP interface sync
Mar 04 18:32:39 pureos systemd[1]: Stopped target Sleep.
Mar 04 18:32:39 pureos systemd[1]: Reached target Suspend.
Mar 04 18:32:39 pureos systemd[1]: Stopped target Suspend.
Mar 04 18:32:39 pureos systemd-logind[500]: Operation ‘sleep’ finished.
Mar 04 18:32:39 pureos systemd-networkd[316]: lo: Reset carrier
Mar 04 18:32:39 pureos ModemManager[599]: [modem0] resume synchronization state (3/4): time interface sync
Mar 04 18:32:39 pureos NetworkManager[486]: [1709569959.2451] manager: sleep: wake requested (sleeping: yes enabled: yes)
Mar 04 18:32:39 pureos ModemManager[599]: [modem0] resume synchronization state (4/4): all done
Mar 04 18:32:39 pureos NetworkManager[486]: [1709569959.2454] device (usb0): state change: unmanaged → unavailable (reason ‘managed’, sys-iface-state: ‘external’)
Mar 04 18:32:39 pureos ModemManager[599]: [modem0] synchronization finished
I also tried to kill all the 3 switches. Nothing helps. It resumes immediately.
If there is no clue, and since it WAS working can I try installing a previous kernel? How can I do this safely?
Suspend works here after activated in system settings AND extended system settings. Do You have any additional software installed which could block the suspend process? For me FE suspend does not start if I make a backup with the internal Backup program to my Nextcloud instance
What is this exactly? I have it enable in Settings → Power → Automatic Suspend (2 minutes on battery power, 2h on Plugged In) and it works very nice.
There is a second settings program where You can allow of using suspend under “experimental features”
Are you willing to share its name?
“Settings” on my phone 
It is a symbol with three symbols like dip switches above another
I have it too. The name is Mobile Settings. And there the feature Eable suspend via the system menu is not enabled, but it works in Settings. Maybe this here in Mobile Settings is just outdated.
Better to allow it also there I think
Do you know the detailed reason, or is it just guessing? As I said, it works perfectly.
There is nothing really documented in this suspend issue
I just enabled suspend in system menu. It does not help. System tries to suspend and comes back on. For me it WAS working a month ago very nicely. I do not remember doing anything strange on my system other than updating. Actually I had put it away for about 10 days and used a Nokia since I had a problem with the twin sim card and was trying to see if the twin sim was working after extending use of its twin in Nokia.
The only thing I know it changed is that I swapped the sim with Nokia, since there was a problem with the primary sim in L5 as described here
But this can not be the problem since it fails to suspend even with all HKS in off position.
Is there a way to have verbose output with
systemctl suspend
on the terminal?
Is there anything interesting in dmesg output when you try to suspend?
The reason it is in phosh-mobile-settings is so that the suspend option appears in the power menu in the top right corner of the pulldown.
[ 168.356987] PM: suspend entry (deep)
[ 168.395685] Filesystems sync: 0.038 seconds
[ 168.396430] Freezing user space processes
[ 168.401890] Freezing user space processes completed (elapsed 0.005 seconds)
[ 168.401917] OOM killer disabled.
[ 168.401920] Freezing remaining freezable tasks
[ 168.405845] Freezing remaining freezable tasks completed (elapsed 0.003 seconds)
[ 168.405856] printk: Suspending console(s) (use no_console_suspend to debug)
[ 168.453324] Disabling non-boot CPUs …
[ 168.453336] Wakeup pending. Abort CPU freeze
[ 168.453338] Non-boot CPUs are not disabled
[ 168.464574] caam 30900000.crypto: registering rng-caam
[ 168.603995] OOM killer enabled.
[ 168.604005] Restarting tasks … done.
[ 168.608954] random: crng reseeded on system resumption
[ 168.653197] thermal thermal_zone3: failed to read out thermal zone (-61)
[ 168.653951] PM: suspend exit
[ 168.654116] PM: suspend entry (s2idle)
[ 168.699597] Filesystems sync: 0.045 seconds
[ 168.700170] Freezing user space processes
[ 168.847922] Freezing user space processes completed (elapsed 0.148 seconds)
[ 168.847946] OOM killer disabled.
[ 168.847951] Freezing remaining freezable tasks
[ 168.849623] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 168.849632] printk: Suspending console(s) (use no_console_suspend to debug)
[ 168.900092] caam 30900000.crypto: registering rng-caam
[ 169.038931] OOM killer enabled.
[ 169.038940] Restarting tasks … done.
[ 169.045505] random: crng reseeded on system resumption
[ 169.062767] thermal thermal_zone3: failed to read out thermal zone (-61)
[ 169.063482] PM: suspend exit