© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
@Fred
Comparing the kernel with/without the patches[1][2], some error messages still present and some didn't. I attached the syslog for more details. Fred, would you mind verifying if the syslog delivers what you want, or some more patches to resolve the remaining error messages are expected?
[1] without the patches in comment#17
ubuntu@kreiken:~$ dmesg | grep hisi_sec2 ; uname -a
[ 35.291450] hisi_sec2 0000:76:00.0: Failed to enable PASID
[ 35.347369] hisi_sec2 0000:76:00.0: Adding to iommu group 53
[ 35.349487] hisi_sec2 0000:76:00.0: fail to alloc uacce (-22)
[ 35.349501] hisi_sec2 0000:76:00.0: enabling device (0000 -> 0002)
[ 35.369709] hisi_sec2 0000:76:00.0: SMMU Opened, the iommu type = 3
[ 35.377772] hisi_sec2 0000:b6:00.0: Failed to enable PASID
[ 35.384833] hisi_sec2 0000:b6:00.0: Adding to iommu group 56
[ 35.387016] hisi_sec2 0000:b6:00.0: fail to alloc uacce (-22)
[ 35.387033] hisi_sec2 0000:b6:00.0: enabling device (0000 -> 0002)
[ 35.402929] hisi_sec2 0000:b6:00.0: SMMU Opened, the iommu type = 3
Linux kreiken 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
[2] with the patches in comment#17
ubuntu@kreiken:~$ dmesg | grep hisi_sec2 ; uname -a
[ 35.755052] hisi_sec2 0000:76:00.0: Adding to iommu group 51
[ 35.762616] hisi_sec2 0000:76:00.0: fail to alloc uacce (-22)
[ 35.762647] hisi_sec2 0000:76:00.0: enabling device (0000 -> 0002)
[ 35.772899] hisi_sec2 0000:76:00.0: SMMU Opened, the iommu type = 3
[ 35.781704] hisi_sec2 0000:b6:00.0: Adding to iommu group 52
[ 35.789265] hisi_sec2 0000:b6:00.0: fail to alloc uacce (-22)
[ 35.789295] hisi_sec2 0000:b6:00.0: enabling device (0000 -> 0002)
[ 35.799282] hisi_sec2 0000:b6:00.0: SMMU Opened, the iommu type = 3
Linux kreiken 5.11.0-38-generic #42~20.