** 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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1976587

Title:
  Fix can't boot up after change to vmd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1976587/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to