NACK[K/U]: [PATCH 0/2][SRU][J/U/OEM-5.17/OEM-5.14] Fix can't boot up after change to vmd
Andrea Righi
andrea.righi at canonical.com
Tue Jul 19 05:19:36 UTC 2022
On Thu, Jun 02, 2022 at 02:32:57PM +0800, Koba Ko wrote:
> BugLink: https://bugs.launchpad.net/bugs/1976587
>
> [Impact]
> the previous commit has been SRUed that enable CONFIG_INTEL_IOMMU_DEFAULT_ON.
> https://bugs.launchpad.net/subiquity/+bug/1937295
> but it would caused the regression with AMD/NVIDIA GPUs.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146
>
> [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.
Already applied to kinetic/linux via upstream updates.
Thanks,
-Andrea
More information about the kernel-team
mailing list