Public bug reported:

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.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux-oem-5.14 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux (Ubuntu Focal)
     Importance: Undecided
         Status: Invalid

** Affects: linux-oem-5.14 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Impish)
     Importance: Undecided
         Status: New

** Affects: linux-oem-5.14 (Ubuntu Impish)
     Importance: Undecided
         Status: Invalid

** Affects: linux (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: linux-oem-5.14 (Ubuntu Jammy)
     Importance: Undecided
         Status: Invalid


** Tags: amd oem-priority originate-from-1956572

** Tags added: amd oem-priority originate-from-1956572

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Focal)
       Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Impish)
       Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
       Status: New => Invalid

-- 
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/1961646

Title:
  On AMD platforms s2idle may not work w/o proper FW

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  Invalid

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

Reply via email to