| 1 |
On Friday 03 Feb 2017 19:40:53 Mick wrote: |
| 2 |
|
| 3 |
> Peter, I recall a similar problem shown in the logs of an i7. and all I |
| 4 |
> did was to enable IOMMU in the kernel, just as a message in the logs |
| 5 |
> recommended. From memory I built in the kernel something like |
| 6 |
> CONFIG_INTEL_IOMMU_DEFAULT_ON as well as some Intel related IOMMU |
| 7 |
> options. I did not pass any options on the kernel line at boot time. The |
| 8 |
> error messages stopped as a result. |
| 9 |
|
| 10 |
$ grep -i iommu /usr/src/linux/.config |
| 11 |
# CONFIG_GART_IOMMU is not set |
| 12 |
CONFIG_CALGARY_IOMMU=y |
| 13 |
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y |
| 14 |
CONFIG_IOMMU_HELPER=y |
| 15 |
CONFIG_IOMMU_API=y |
| 16 |
CONFIG_IOMMU_SUPPORT=y |
| 17 |
CONFIG_IOMMU_IOVA=y |
| 18 |
# CONFIG_AMD_IOMMU is not set |
| 19 |
CONFIG_INTEL_IOMMU=y |
| 20 |
CONFIG_INTEL_IOMMU_SVM=y |
| 21 |
CONFIG_INTEL_IOMMU_DEFAULT_ON=y |
| 22 |
CONFIG_INTEL_IOMMU_FLOPPY_WA=y |
| 23 |
# CONFIG_IOMMU_STRESS is not set |
| 24 |
$ |
| 25 |
|
| 26 |
That looks all right to me, no? |
| 27 |
|
| 28 |
-- |
| 29 |
Regards |
| 30 |
Peter |
Archives