1 |
On Saturday 04 Feb 2017 11:11:43 Mick wrote: |
2 |
> On Saturday 04 Feb 2017 10:17:13 Peter Humphrey wrote: |
3 |
> > On Friday 03 Feb 2017 19:40:53 Mick wrote: |
4 |
> > > Peter, I recall a similar problem shown in the logs of an i7. and |
5 |
> > > all I |
6 |
> > > did was to enable IOMMU in the kernel, just as a message in the logs |
7 |
> > > recommended. From memory I built in the kernel something like |
8 |
> > > CONFIG_INTEL_IOMMU_DEFAULT_ON as well as some Intel related |
9 |
IOMMU |
10 |
> > > options. I did not pass any options on the kernel line at boot time. |
11 |
> > > The |
12 |
> > > error messages stopped as a result. |
13 |
> > |
14 |
> > $ grep -i iommu /usr/src/linux/.config |
15 |
> > # CONFIG_GART_IOMMU is not set |
16 |
> > CONFIG_CALGARY_IOMMU=y |
17 |
> > CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y |
18 |
> > CONFIG_IOMMU_HELPER=y |
19 |
> > CONFIG_IOMMU_API=y |
20 |
> > CONFIG_IOMMU_SUPPORT=y |
21 |
> > CONFIG_IOMMU_IOVA=y |
22 |
> > # CONFIG_AMD_IOMMU is not set |
23 |
> > CONFIG_INTEL_IOMMU=y |
24 |
> > CONFIG_INTEL_IOMMU_SVM=y |
25 |
> > CONFIG_INTEL_IOMMU_DEFAULT_ON=y |
26 |
> > CONFIG_INTEL_IOMMU_FLOPPY_WA=y |
27 |
> > # CONFIG_IOMMU_STRESS is not set |
28 |
> > $ |
29 |
> > |
30 |
> > That looks all right to me, no? |
31 |
> |
32 |
> The only difference is I have not set CONFIG_INTEL_IOMMU_SVM on my |
33 |
system. |
34 |
|
35 |
Now I've just passed intel_iommu=off on the kernel command line. I'll see how |
36 |
that behaves; at least I don't get all those errors (warnings?) in dmesg. |
37 |
|
38 |
-- |
39 |
Regards |
40 |
Peter |