Fix can't boot up after change to vmd
Bug #1976587 reported by
koba
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
koba | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
koba | ||
Kinetic |
Fix Released
|
Undecided
|
koba | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
koba | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
koba | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
the previous commit has been SRUed that enable CONFIG_
https:/
but it would caused the regression with AMD/NVIDIA GPUs.
https:/
https:/
[Fix]
Revert the vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU.")
Assign VMD irq domain before enumeration, irq domain comes from pci driver.
[Test Case]
1. In BIOS, change to VMD
2. Check if SKU could boot-up.
[Where problems could occur]
it reduce the affected region to only VMD.
CVE References
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux (Ubuntu Kinetic): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
description: | updated |
tags: | added: oem-priority originate-from-1967153 somerville |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal verification-done-jammy removed: verification-needed-focal verification-needed-jammy |
Changed in linux (Ubuntu Focal): | |
status: | New → Invalid |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux (Ubuntu Kinetic): | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 5.17/5. 17.0-1012. 13 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' to 'verification- done-jammy' . If the problem still exists, change the tag 'verification- needed- jammy' to 'verification- failed- jammy'.
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!