** Description changed: For some of the arm64 systems arm-smmu driver doesn't seem to work with older versions of the firmware where it encounters "mmu-masters" in the device-tree. In this case, kernel is unable to map simple drm device and fail to boot (Note that for "DMA_API" it works fine). See, drivers/iommu/arm/arm- smmu/arm-smmu.c:arm_smmu_device_dt_probe() for more information. - I have seen the error for the following arm64 instances in testflinger: moigno, igor, egede. Updating the firmware seems like one of the possible solutions. But - will bionic be able to boot afterwards? + I have seen the error for the following arm64 instances in testflinger: + moigno, igor, egede. Updating the firmware seems like one of the + possible solutions. But will bionic be able to boot afterwards? I have seen this error in 6.8 kernels (noble+jammy). However, both series should fail regardless of the kernel version. Focal can be different since "CONFIG_ARM_SMMU_LEGACY_DT_BINDINGS" config option is not defined there. If Focal works, we can remove this config option from Jammy and Noble. See error messages below for more information.
-- 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/2088458 Title: noble/jammy arm-smmu and firmware discrepancy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: For some of the arm64 systems arm-smmu driver doesn't seem to work with older versions of the firmware where it encounters "mmu-masters" in the device-tree. In this case, kernel is unable to map simple drm device and fail to boot (Note that for "DMA_API" it works fine). See, drivers/iommu/arm/arm-smmu/arm-smmu.c:arm_smmu_device_dt_probe() for more information. I have seen the error for the following arm64 instances in testflinger: moigno, igor, egede. Updating the firmware seems like one of the possible solutions. But will bionic be able to boot afterwards? I have seen this error in 6.8 kernels (noble+jammy). However, both series should fail regardless of the kernel version. Focal can be different since "CONFIG_ARM_SMMU_LEGACY_DT_BINDINGS" config option is not defined there. If Focal works, we can remove this config option from Jammy and Noble. See error messages below for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088458/+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
