Attached is a boot log w/ the fixed kernel that shows the SMMU being discovered, the system successfully mounting the root disk, etc. However, the system does seem to hang at the end with the networking failing to come up.
This is an improvement, and booting in non-ACPI mode shows no regressions, so I'll mark this as verified. However, it does look like there is more needed to get to a fully functional system in ACPI-mode. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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: Fix Committed Status in linux source package in Zesty: Fix Committed 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
