(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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
