(In reply to Ferry Toth from comment #33) > > echo deep > /sys/power/mem_sleep > > rtcwake -m mem -s 30? > > Looking from blinking LED goes into suspend. Waking takes me directly to > BIOS screen. > > > echo s2idle > /sys/power/mem_sleep > > rtcwake -m freeze -s 30? > > Looking from non-blinking LED is not really suspended, except everything > else looks suspended. > Pressing keyboard wakes normally. > > journalctl -b -e: > apr 13 19:36:15 chromium kernel: PM: suspend entry (s2idle) > apr 13 19:36:15 chromium kernel: Filesystems sync: 0.000 seconds > apr 13 19:36:15 chromium kernel: Freezing user space processes ... (elapsed > 0.002 seconds) done. > apr 13 19:36:15 chromium kernel: OOM killer disabled. > apr 13 19:36:15 chromium kernel: Freezing remaining freezable tasks ... > (elapsed 0.001 seconds) done. > apr 13 19:36:15 chromium kernel: printk: Suspending console(s) (use > no_console_suspend to debug) > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Stopping disk > apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt blocked > apr 13 19:36:15 chromium kernel: ACPI: EC: interrupt unblocked > apr 13 19:36:15 chromium kernel: hpet_rtc_timer_reinit: 14 callbacks > suppressed > apr 13 19:36:15 chromium kernel: hpet: Lost 6192 RTC interrupts > apr 13 19:36:15 chromium kernel: ath: phy0: ASPM enabled: 0x43 > apr 13 19:36:15 chromium kernel: sd 0:0:0:0: [sda] Starting disk > apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Resetting device > apr 13 19:36:15 chromium kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 > SControl 300) > apr 13 19:36:15 chromium kernel: ata1.00: configured for UDMA/100 > apr 13 19:36:15 chromium kernel: atmel_mxt_ts 2-004a: Wait for completion > timed out. > apr 13 19:36:15 chromium kernel: OOM killer enabled. > apr 13 19:36:15 chromium kernel: Restarting tasks ... done. > apr 13 19:36:15 chromium kernel: PM: suspend exit
suspend to idle works as expected. Could you switch back to linux v5.0, as you mentioned in Comment 9, and check what is the default suspend mode : cat /sys/power/mem_sleep and try echo deep > /sys/power/mem_sleep rtcwake -m mem -s 30 echo s2idle > /sys/power/mem_sleep rtcwake -m freeze -s 30 I was thinking if the default suspend mode is s2idle on v5.0, or your bios has implicitly been adjusted, as there's no chance for OS to control the flow once suspended to S3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: <info> manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: <info> device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: <info> device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: <info> device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: <info> manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
