[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Jeff Lane | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Undecided
|
Michael Reed | ||
Mantic |
Fix Released
|
Undecided
|
Jeff Lane | ||
Noble |
Fix Released
|
Undecided
|
Jeff Lane |
Bug Description
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID ffff
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID ffff
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: Clean up domain before enumeration"). The root cause is that VMD driver tries to clear a PCI configuration space range when resetting a VMD domain (https:/
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu 22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology --> Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology --> Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
https:/
affects: | ubuntu → linux-hwe-5.19 (Ubuntu) |
Changed in linux (Ubuntu Kinetic): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu Lunar): | |
assignee: | nobody → Jeff Lane (bladernr) |
Changed in linux (Ubuntu Mantic): | |
assignee: | nobody → Jeff Lane (bladernr) |
Changed in linux (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in linux (Ubuntu Mantic): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Mantic): | |
status: | Invalid → Fix Released |
information type: | Private → Private Security |
information type: | Private Security → Public Security |
description: | updated |
Changed in linux (Ubuntu Lunar): | |
assignee: | Jeff Lane (bladernr) → Michael Reed (mreed8855) |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Lunar): | |
status: | In Progress → Fix Committed |
Kernels seen 5.19, 6.2 so far.
Can you also try 5.15 (22.04 GA) and 5.4 (20.04 GA) as both of those are certified on both 22.04 and 20.04