https://bugzilla.novell.com/show_bug.cgi?id=817210
https://bugzilla.novell.com/show_bug.cgi?id=817210#c13
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
InfoProvider| |gadm@avalon-island.ru
--- Comment #13 from Jan Beulich 2013-05-08 13:03:41 UTC ---
Now back to the log in #5: You didn't specify any graphics mode for Xen to use,
so vesafb can't have come into the picture there.
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.
Also, #11 would also need to be accompanied by a matching hypervisor+kernel log
with "iommu=debug" in place, so we can see what respective faults may be
occurring there.
--
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.