New ACPI identifiers for ThunderX SMMU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
dann frazier | ||
Zesty |
Fix Released
|
High
|
dann frazier |
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.
CVE References
Changed in linux (Ubuntu Zesty): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Fix Committed |
This is fixed by the following commit in linux-next:
commit 84c24379a783c51 4e5ff7c8fc8a21c f8d64fd05f
Author: Robin Murphy <email address hidden>
Date: Mon Jun 19 16:41:56 2017 +0100
iommu/arm-smmu: Plumb in new ACPI identifiers