Enable ASPM for NVMe behind VMD
Bug #2034504 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
OEM Priority Project |
New
|
Undecided
|
Unassigned | |||
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
New
|
Undecided
|
Unassigned | |||
Lunar |
Fix Committed
|
Low
|
Unassigned | |||
Mantic |
Fix Released
|
Low
|
Unassigned | |||
linux-oem-6.1 (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Released
|
Low
|
Unassigned | |||
Lunar |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned | |||
linux-oem-6.5 (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Released
|
Low
|
Unassigned | |||
Lunar |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified.
That causes higher overall power consumption.
[Fix]
Allow ASPM to be enabled.
While at this, remove old cruft that can interfere upstream VMD driver.
[Test]
Check the value of `/sys/kernel/
[Where problems could occur]
Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled.
CVE References
Changed in linux (Ubuntu Lunar): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Mantic): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Lunar): | |
importance: | Undecided → Low |
Changed in linux (Ubuntu Mantic): | |
importance: | Undecided → Low |
Changed in linux-oem-6.1 (Ubuntu Jammy): | |
status: | New → Confirmed |
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): | |
importance: | Undecided → Low |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in linux-oem-6.5 (Ubuntu Lunar): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
tags: | added: oem-priority originate-from-2033330 somerville |
tags: | added: originate-from-2032928 |
Changed in linux-oem-6.1 (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-jammy-linux-oem-6.1 removed: verification-needed-jammy-linux-oem-6.1 |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Lunar): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Mantic): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-lunar-linux removed: verification-needed-lunar-linux |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 6.1/6.1. 0-1023. 23 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!