Public bug reported:

[Impact]
With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

[Test Case]
Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

[Regression Risk]
The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

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

** Affects: linux (Ubuntu Zesty)
     Importance: High
     Assignee: dann frazier (dannf)
         Status: In Progress

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

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

** Changed in: linux (Ubuntu Zesty)
   Importance: Undecided => High

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

-- 
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/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

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