[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Using debug-key 'o: Dump IOMMU p2m table, locks up machine
Hello Jan, Monday, September 3, 2012, 10:21:04 AM, you wrote: >>>> On 02.09.12 at 10:43, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote: >> I have attached new output from xl dmesg, this time with iommu=debug on (the >> option changed from 4.1 to 4.2). > This one >>(XEN) [2012-09-02 00:55:02] traps.c:3156: GPF (0060): ffff82c48015c9ee -> >>ffff82c480224b13 > also worries me. While Xen gracefully recovers from it, these > messages still generally indicate a problem somewhere. Could > you resolve the addresses to file:line tuples? And, assuming > this happens in the context of doing something on behalf of > the guest in the context of a guest vCPU, could you also > check what guest side action triggers this (e.g. by adding a > call to show_execution_state() alongside the printing of the > message)? If you could elaborate a bit abouw HOW :-) >From what i recall i also had these since some time on xen 4.1 too. Probably a >kernel thing, in about 3.5 or 3.6 is my estimation, will see if i can find out >some more today or tomorrow. > Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |