Clear PCI errors left from BIOS
Bug #1981173 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Low
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Low
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Low
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Errors like Master Abort can be flagged before setting up PCI devices.
[Fix]
Clear PCI status that BIOS handed over to the OS.
[Test]
Using `lspci`, no more errors after boot.
[Where problems could occur]
If there's any driver's probe routine depends on PCI status to have
different behavior, this can cause some cracks. There doesn't seem to be
any driver doing such insane thing though.
CVE References
affects: | linux-firmware (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu Focal): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu Jammy): | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in linux-oem-5.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: oem-priority originate-from-1968671 sutton |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in linux (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Changed in hwe-next: | |
importance: | Undecided → Critical |
status: | New → Fix Committed |
Changed in hwe-next: | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux-oem-5.14 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
To post a comment you must log in.
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 1981173
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.