https://bugzilla.novell.com/show_bug.cgi?id=817210
https://bugzilla.novell.com/show_bug.cgi?id=817210#c14
Андрей Кольчугин
The fault addresses (0xbf800000) point into hidden RAM (according to my guessing from the E820 map), and hence there being accesses to such memory invisible to Xen implies incomplete IOMMU related tables being provided by the firmware. Hence I don't think it is a Xen bug that "iommu=dom0-strict" doesn't work on that system. To hopefully clarify this, telling us what device is 0000:00:02.0 and attaching the contents of /proc/iomem when running a native kernel will be necessary. I had found my old hard drive with openSuSE v12.2 installed, attached it to system in question and have just booted native Linux kernel with intel_iommu=on -- as I have mentioned before, Linux kernel v3.1 boots flawlessly with KMS/X11 even with IOMMU enabled -- albeit immediately locks up hard when I start, for example, (in)famous 'glxgears', but anyway, it is a regression for openSuSE v12.3 -- newer kernel locks up during boot.
It seems to me that your guesses more than plausible: kernel whines about DMA Write Errors: === DMAR:[DMA Write] Request device [00:02.0] fault addr bffff000 DMAR:[fault reason 05] PTE Write access is not set DRHD: handling fault status reg 3 === But memory region DMA Remapping Engine complains about is ABSENT in /proc/iomem completely! What can be wrong with it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.