All of these commits are in v5.15.25 from stable backports, so no jammy
tasks for generic kernel either.
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1961646
Title:
On AMD platforms s2idle may not work w/o proper FW
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Impish:
Won't Fix
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux-oem-5.17 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
It was raised because of a community member using a Lenovo platform
having very odd s2idle failures.
It was later debugged that it was caused by them choosing "Linux" mode
in Lenovo BIOS setup rather than "Windows" mode and then choosing
"s2idle" in /sys/power/mem_sleep.
- In "Linux" mode there is both "deep" and "s2idle" offered in
/sys/power/mem_sleep.
- In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep.
That is by default no matter if the OEM offers S3 or S2idle
/sys/power/mem_sleep will contain "s2idle", but on AMD platforms
"s2idle" only works if the hardware has been configured properly by
the firmware. The outward indications of this being configured
properly are the FADT low power idle bit being set and the uPEP ACPI
device being populated, which is what this patch now checks for.
So now if a user has the firmware of the machine configured for S3
then they will only see "deep" on AMD systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1961646/+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
