Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | |||
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Invalid
|
Undecided
|
Unassigned | |||
Lunar |
In Progress
|
Undecided
|
koba | |||
Mantic |
In Progress
|
Undecided
|
koba | |||
linux-oem-6.1 (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Released
|
Undecided
|
Unassigned | |||
Lunar |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned | |||
linux-oem-6.5 (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Committed
|
Undecided
|
koba | |||
Lunar |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
System can't enter suspend on AHCI mode,
the CPU FAN and System FAN is running, PSU LED is on.
When fail to enter suspend, remove ODD, the system can successfully enter suspend again.
[Fix]
Enable LPM on Alder Lake-P AHCI.
[Test Cases]
1. enabled AHCI on target machine.
2. boot with kernel applied fix.
3. suspend then check slp_s0_
~~~
u@ubuntu:~$ sudo cat /sys/kernel/
4951200
Package C2 : 63571033
Package C3 : 6212
Package C6 : 5633477
Package C7 : 0
Package C8 : 0
Package C9 : 0
Package C10 : 5255561
u@ubuntu:~$ sudo rtcwake -m mem -s 10
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/rtc0
u@ubuntu:~$ sudo cat /sys/kernel/
12965280
Package C2 : 75052691
Package C3 : 46989
Package C6 : 8108332
Package C7 : 0
Package C8 : 0
Package C9 : 0
Package C10 : 13628111
~~~
[where the issue could happen]
Medium, Intel promise there's no issue of ADL AHCI and
they will take responsibility after regression.
Intel also take LPM as POR so they will fix any issues.
CVE References
description: | updated |
tags: | added: flying-fox oem-priority originate-from-2025203 |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
tags: | added: originate-from-2027772 |
Changed in linux (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in linux (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Lunar): | |
assignee: | nobody → koba (kobako) |
Changed in linux (Ubuntu Mantic): | |
assignee: | nobody → koba (kobako) |
description: | updated |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-6.5 (Ubuntu Lunar): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu Lunar): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux-oem-6.1 (Ubuntu Jammy): | |
status: | New → Fix Committed |
This bug is awaiting verification that the linux-oem- 6.1/6.1. 0-1024. 24 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy-linux- oem-6.1' to 'verification- done-jammy- linux-oem- 6.1'. If the problem still exists, change the tag 'verification- needed- jammy-linux- oem-6.1' to 'verification- failed- jammy-linux- oem-6.1' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!