| 2023-05-18 03:42:37 |
Adrian Huang |
bug |
|
|
added bug |
| 2023-05-18 03:42:37 |
Adrian Huang |
attachment added |
|
OS log https://bugs.launchpad.net/bugs/2020022/+attachment/5673714/+files/119N_UBUNTU22.04.2_5.19.txt |
|
| 2023-05-18 03:42:50 |
Adrian Huang |
information type |
Public |
Private Security |
|
| 2023-05-18 03:43:10 |
Adrian Huang |
information type |
Private Security |
Private |
|
| 2023-05-18 03:44:01 |
Adrian Huang |
summary |
OS cannot boot successfully when enabling VMD in UEFI setup |
[22.04.2] OS cannot boot successfully when enabling VMD in UEFI setup |
|
| 2023-05-18 03:45:59 |
Adrian Huang |
summary |
[22.04.2] OS cannot boot successfully when enabling VMD in UEFI setup |
[22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup |
|
| 2023-05-18 03:49:03 |
Adrian Huang |
attachment added |
|
[23.10] OS log https://bugs.launchpad.net/ubuntu/+bug/2020022/+attachment/5673716/+files/119N_UBUNTU-23.10.txt |
|
| 2023-05-18 03:49:23 |
Adrian Huang |
description |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
* 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 kernel? |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
* 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? |
|
| 2023-05-24 00:25:24 |
Adrian Huang |
affects |
ubuntu |
linux-hwe-5.19 (Ubuntu) |
|
| 2023-05-24 00:29:15 |
Adrian Huang |
bug |
|
|
added subscriber Jeff Lane |
| 2023-05-24 00:36:37 |
Jeff Lane |
linux-hwe-5.19 (Ubuntu): status |
New |
Incomplete |
|
| 2023-05-24 00:41:05 |
Jeff Lane |
affects |
linux-hwe-5.19 (Ubuntu) |
linux (Ubuntu) |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
bug task added |
|
linux (Ubuntu Mantic) |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
bug task added |
|
linux (Ubuntu Lunar) |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-05-24 00:41:33 |
Jeff Lane |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2023-05-24 06:41:50 |
Adrian Huang |
attachment added |
|
Kernel v5.15 does not have the issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5675221/+files/119N_UBUNTU22.04.2-kernel-v5.15.txt |
|
| 2023-05-24 06:42:28 |
Adrian Huang |
attachment added |
|
Kernel v5.4 does not have the issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5675222/+files/119N_UBUNTU20.04.6_5.4.0_PASS.txt |
|
| 2023-05-24 14:26:47 |
Jeff Lane |
bug |
|
|
added subscriber Canonical Kernel Team |
| 2023-07-19 00:09:25 |
Jeff Lane |
linux (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-07-31 15:40:47 |
Jeff Lane |
linux (Ubuntu Lunar): assignee |
|
Jeff Lane (bladernr) |
|
| 2023-07-31 15:40:49 |
Jeff Lane |
linux (Ubuntu Mantic): assignee |
|
Jeff Lane (bladernr) |
|
| 2023-07-31 15:41:00 |
Jeff Lane |
linux (Ubuntu Lunar): status |
New |
In Progress |
|
| 2023-07-31 15:41:02 |
Jeff Lane |
linux (Ubuntu Mantic): status |
Incomplete |
In Progress |
|
| 2023-07-31 16:44:52 |
Jeff Lane |
linux (Ubuntu Mantic): status |
In Progress |
Invalid |
|
| 2023-08-01 19:39:02 |
Jeff Lane |
bug |
|
|
added subscriber Michael Reed |
| 2023-08-01 19:51:01 |
Jeff Lane |
linux (Ubuntu Mantic): status |
Invalid |
Fix Released |
|
| 2023-08-10 02:06:33 |
Michael Reed |
description |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
* 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? |
[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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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 ]
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022 |
|
| 2023-08-10 02:06:53 |
Michael Reed |
summary |
[22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup |
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup |
|
| 2023-08-10 02:56:17 |
Adrian Huang |
information type |
Private |
Private Security |
|
| 2023-08-10 03:01:23 |
Adrian Huang |
information type |
Private Security |
Public Security |
|
| 2023-08-24 05:32:30 |
Adrian Huang |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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 ]
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022 |
[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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022 |
|
| 2023-08-24 05:42:06 |
Adrian Huang |
attachment added |
|
2304_6.1.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5694553/+files/2304_6.1.txt |
|
| 2023-09-25 10:56:36 |
Adrian Huang |
attachment added |
|
[23.10] v6.5 kernel https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5704279/+files/dmesg.log |
|
| 2023-12-06 21:42:02 |
Michael Reed |
nominated for series |
|
Ubuntu Noble |
|
| 2023-12-06 21:42:02 |
Michael Reed |
bug task added |
|
linux (Ubuntu Noble) |
|
| 2023-12-12 20:44:04 |
Jeff Lane |
linux (Ubuntu Lunar): assignee |
Jeff Lane (bladernr) |
Michael Reed (mreed8855) |
|
| 2023-12-12 21:10:55 |
Michael Reed |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022 |
[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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022 |
|
| 2023-12-12 21:11:53 |
Michael Reed |
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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022 |
[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://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544), which leads to the failure.
[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://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022 |
|
| 2023-12-13 12:55:38 |
Adrian Huang |
attachment added |
|
dmesg-6.2.0-39_enableVMD https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5728888/+files/6.2.0-39_enableVMD.txt |
|
| 2024-01-05 11:32:40 |
Roxana Nicolescu |
linux (Ubuntu Lunar): status |
In Progress |
Fix Committed |
|
| 2024-01-09 18:21:59 |
Ubuntu Kernel Bot |
tags |
|
kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux |
|
| 2024-01-25 20:38:21 |
Brian Murray |
linux (Ubuntu Lunar): status |
Fix Committed |
Won't Fix |
|
