There can be either s3 or s2idle: 1. let's first identify the default sleep type such as
$ cat /sys/power/mem_sleep [s2idle] deep 2. use rtcwake to trigger a sleep, if this works, dmesg will show "PM: suspend entry (s2idle)" or "PM: suspend entry (deep)" $ sudo rtcwake -m mem -s 30 3. If s2idle is the default, let's force fwts to use it and verify whether the bug persists $ sudo fwts s3 --s3-sleep-type=s2idle --s3-sleep-delay=30 Note: fwts may use "deep" as default" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956914 Title: Can't resume from suspend on some specific systems using fwts 21.12 To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1956914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
