Public bug reported:

[Impact]
ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize 
them, which can e.g. prevent detected device errors from being reported.

[Test Case]
dmesg | grep "failed to allocate MSIs"
grep arm-smmu-v3 /proc/interrupts

[Fix]
Upstream fixes that add support for the SMMUv3 device ID mapping index - which 
is required for MSI support - need to be included.

[Regression Risk]
By enabling these interrupts, we're allowing code to run that previously 
didn't, which could potentially do bad things. However, the interrupt handlers 
look pretty simple/straightforward, and I haven't seen any problems on a system 
that uses them w/ the fixes applied.

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: dann frazier (dannf)
         Status: Fix Released

** Affects: linux (Ubuntu Bionic)
     Importance: Undecided
     Assignee: dann frazier (dannf)
         Status: In Progress

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
     Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  arm-smmu-v3 arm-smmu-v3.1.auto: failed to allocate MSIs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize 
them, which can e.g. prevent detected device errors from being reported.

  [Test Case]
  dmesg | grep "failed to allocate MSIs"
  grep arm-smmu-v3 /proc/interrupts

  [Fix]
  Upstream fixes that add support for the SMMUv3 device ID mapping index - 
which is required for MSI support - need to be included.

  [Regression Risk]
  By enabling these interrupts, we're allowing code to run that previously 
didn't, which could potentially do bad things. However, the interrupt handlers 
look pretty simple/straightforward, and I haven't seen any problems on a system 
that uses them w/ the fixes applied.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785282/+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