Continuous tracking for PTE Read Access is not set

The relevant information is displayed in connection with the BIOS or PCI, most likely the motherboard's exception:

I tried the command line parameter:i915.i915_enable_rc6=0
But without success. Is it still useful for Ivy Bridge CPU

Another (rather unlikely, but I'll still mention it just in case) reason could is that you ' re using Igb_uio
Module that's really old (I don ' t remember when Igb_uio gained IOMMU support, probably 1.4.x), which are
Why I asked on DPDK version, but since your ' re using 1.6.0 you should be fine.

Please test with Intel_iommu=igfx_off added to the kernel cmdline. Probably broken Dmar tables in your BIOS, so please also check

For a BIOS upgrade

Does it work on 3.17-RC1? Is all of the 8169 NICs on bus and running?
Provide LSPCI-VV info for 04:00.0

LSPCI-VVS 04:00.0
04:00.0 PCI Bridge:asmedia Technology Inc. asm1083/1085 PCIe to PCI Bridge
(Rev 03) (Prog-if xx [Normal decode])
control:i/o+ mem+ busmaster+ speccycle-memwinv-vgasnoop-parerr-
stepping-serr-fastb2b-disintx-
status:cap+ 66mhz-udf-fastb2b-parerr-devsel=fast >tabort-<tabort-
<mabort->serr-<perr-intx-
latency:0, Cache line size:64 bytes
bus:primary=04, secondary=05, subordinate=05, sec-latency=32
I/O behind bridge:0000c000-0000cfff
Memory behind BRIDGE:F7800000-F78FFFFF
Secondary status:66mhz+ fastb2b-parerr-devsel=fast >tabort-<tabort-
<mabort+ <serr-<perr-
bridgectl:parity-serr-noisa-vga-mabort->reset-fastb2b-
pridisctmr-secdisctmr-disctmrstat-disctmrserren-
Capabilities: [MSI:ENABLE-COUNT=1/1] maskable-64bit+
address:0000000000000000 data:0000
Capabilities: [+] Power Management version 3
flags:pmeclk-dsi+ d1+ d2+ auxcurrent=0ma
PME (d0+,d1+,d2+,d3hot+,d3cold+)
Status:d0 nosoftrst+ pme-enable-dsel=0 dscale=0 pme-
Capabilities: [+] Express (v1) pci/pci-x Bridge, MSI 00
Devcap:maxpayload bytes, Phantfunc 0, Latency l0s <64ns,
L1 <1us
Exttag-attnbtn-attnind-pwrind-rbe+ flreset-
Devctl:report errors:correctable-non-fatal-fatal-
unsupported-
rlxdord-exttag-phantfunc-auxpwr-nosnoop+
brconfrtry-
Maxpayload bytes, Maxreadreq bytes
devsta:correrr-uncorrerr+ fatalerr-unsuppreq+ auxpwr-
transpend-
Lnkcap:port #1, Speed 2.5gt/s, Width x1, ASPM l0s L1, Latency
L0 <2us, L1 <2us
clockpm-surprise-llactrep-bwnot-
LNKCTL:ASPM Disabled; disabled-retrain-commclk-
extsynch-clockpm-autwiddis-bwint-autbwint-
Lnksta:speed 2.5gt/s, Width x1, trerr-train-slotclk-
dlactive-bwmgmt-abwmgmt-
Capabilities: [C0] Subsystem:micro-star International Co., Ltd. Device
7758
Capabilities: [V1] Virtual Channel
Caps:lpevc=0 Refclk=100ns Patentrybits=1
arb:fixed-wrr32-wrr64-wrr128-
Ctrl:arbselect=fixed
status:inprogress-
vc0:caps:patoffset=00 Maxtimeslots=1 rejsnooptrans-
arb:fixed-wrr32-wrr64-wrr128-twrr128-wrr256-
Ctrl:enable+ id=0 arbselect=fixed tc/vc=01
status:negopending-inprogress-

79305f iommu/vt-d: Update to use PCI DMA aliases
E17F9FF iommu/vt-d: Use Iommu_group_get_for_dev ()
104A1C1 iommu/core:create Central Iommu group Lookup/creation interface

Ok, then it's probably not a result of the Pcie-to-pci bridge since 05:00.0 is
The correct requester ID for all the devices behind the bridge. Unfortunately
That means, the problem may is fixable. We ' re only seeing reads to a
Single address, which could mean the NIC is using this read to synchronize
Transaction ordering, ex. Using a DMA read to flush a DMA write from the
Device. If the NIC driver has visibility of this address, then it could
Attempt to does a coherent mapping for the device (s) to avoid the fault. If it
Doesn ' t, then these NICs may simply is incompatible with the IOMMU.

is these 3 separate NICs plugged to PCI slots on the motherboard or was this
A single Triple-port card with embedded Pcie-to-pci bridge?

You might is able to run the IOMMU in passthrough mode with IOMMU=PT
R8169.use_dac=1, but note the warning in modinfo "Use_dac:enable PCI DAC.
Unsafe on the + bit PCI slot. " Unfortunately if you don ' t enable USE_DAC and then
Intel_iommu would ignore the passthrough option for these devices.

Also Note that this problem have nothing to does with VIRTUALIZATION/KVM.
Drivers/network or perhaps Drivers/pci would be a more appropriate
Classification

Since you ' re apparently trying-use vt-d on the This system for KVM and therefore
Presumably device assignment, I ' ll note that you'll never be able to
Successfully assign the conventional PCI devices separately between guests or
Between host and guests. The IOMMU does not has the granularity to create
Separate IOMMU domains per PCI slot in this topology. Also, some (all?)
Realtek NICs has some strange backdoors to PCI configuration space
them poor targets for PCI device assignment:

I think ASUS Iommu errors is all the same issue. Bad BIOSes. I ' ve had a p45m (Asus laptop) and a new Core i5 desktop (ASUS

Motherboard) has Dmar errors spewing out from the kernel. Turning off vt-d solves the problem. USB becomes broken on the

Desktop with vt-d on. It's unfortunate that this issue is not the seen on 2.6.30 and lower kernels. Would a work-around be applied to

2.6.31+ kernels or is kernel maintainers going to give us a cold shoulder and say talk to ASUS

Continuous tracking for PTE Read Access is not set