On Saturday 04 Feb 2017 11:11:43 Mick wrote: > On Saturday 04 Feb 2017 10:17:13 Peter Humphrey wrote: > > On Friday 03 Feb 2017 19:40:53 Mick wrote: > > > Peter, I recall a similar problem shown in the logs of an i7. and > > > all I > > > did was to enable IOMMU in the kernel, just as a message in the logs > > > recommended. From memory I built in the kernel something like > > > CONFIG_INTEL_IOMMU_DEFAULT_ON as well as some Intel related IOMMU > > > options. I did not pass any options on the kernel line at boot time. > > > The > > > error messages stopped as a result. > > > > $ grep -i iommu /usr/src/linux/.config > > # CONFIG_GART_IOMMU is not set > > CONFIG_CALGARY_IOMMU=y > > CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y > > CONFIG_IOMMU_HELPER=y > > CONFIG_IOMMU_API=y > > CONFIG_IOMMU_SUPPORT=y > > CONFIG_IOMMU_IOVA=y > > # CONFIG_AMD_IOMMU is not set > > CONFIG_INTEL_IOMMU=y > > CONFIG_INTEL_IOMMU_SVM=y > > CONFIG_INTEL_IOMMU_DEFAULT_ON=y > > CONFIG_INTEL_IOMMU_FLOPPY_WA=y > > # CONFIG_IOMMU_STRESS is not set > > $ > > > > That looks all right to me, no? > > The only difference is I have not set CONFIG_INTEL_IOMMU_SVM on my system.
Now I've just passed intel_iommu=off on the kernel command line. I'll see how that behaves; at least I don't get all those errors (warnings?) in dmesg. -- Regards Peter
