On AMD platforms s2idle may not work w/o proper FW
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
Invalid
|
Undecided
|
Unassigned | ||
| Impish |
Won't Fix
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
| linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Focal |
Fix Released
|
Undecided
|
Unassigned | ||
| Impish |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Invalid
|
Undecided
|
Unassigned | ||
| linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Focal |
Invalid
|
Undecided
|
Unassigned | ||
| Impish |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
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/
- In "Linux" mode there is both "deep" and "s2idle" offered in /sys/power/
- In "Windows" mode there is only "s2idle" offered in /sys/power/
That is by default no matter if the OEM offers S3 or S2idle /sys/power/
So now if a user has the firmware of the machine configured for S3 then they will only see "deep" on AMD systems.
| tags: | added: amd oem-priority originate-from-1956572 |
| 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 |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu Impish): | |
| status: | New → Incomplete |
| You-Sheng Yang (vicamo) wrote | #2 |
| Mario Limonciello (superm1) wrote | #3 |
| Changed in linux-oem-5.17 (Ubuntu Impish): | |
| status: | New → Invalid |
| Changed in linux-oem-5.17 (Ubuntu Focal): | |
| status: | New → Invalid |
| Changed in linux-oem-5.17 (Ubuntu Jammy): | |
| status: | New → Fix Released |
| Mario Limonciello (superm1) wrote | #4 |
| 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 |
| Mario Limonciello (superm1) wrote | #5 |
| Changed in linux-oem-5.14 (Ubuntu Focal): | |
| status: | New → Fix Released |
| Changed in hwe-next: | |
| status: | New → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1961646
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.