It can be the result of the following commit which introduced "s3-sleep-
type" and used "deep" sleep as default in fwts 21.11.00. If 21.10.00
does not have the issue we can also certain this is the root cause.
commit 713284e505287611c7e1e6ae61254de3035433b5
Author: Ivan Hu <ivan...@canonical.com>
Date: Fri Nov 19 17:20:25 2021 +0800
s3: add sleep type setting for testing with s3 or s2idle
Add s3-sleep-type for select test with s3 or s2idle.
i.e. fwts s3 --s3-sleep-type=s2idle
If sleep type is not specified, test with s3 by default.
And it will restore system sleep type settings after testing.
Signed-off-by: Ivan Hu <ivan...@canonical.com>
Acked-by: Alex Hung <alex.h...@canonical.com>
If 713284e50528 is the root cause, a solution can land in either fwts or
checkbox (i.e run "sudo fwts s3 --s3-sleep-type=s2idle --s3-sleep-delay=30").
We can start a conversation for a appropriate fix.
--
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
