WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Getting mm.c errors from xl dmesg on certain hardware

To: "Anthony Wright" <anthony@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Getting mm.c errors from xl dmesg on certain hardware
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Fri, 23 Sep 2011 11:46:01 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Fri, 23 Sep 2011 03:46:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E7C5F8B.6050509@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4E7C5F8B.6050509@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 23.09.11 at 12:29, Anthony Wright <anthony@xxxxxxxxxxxxxxx> wrote:
> Konrad Rzeszutek Wilk wrote:
> 
>>> (XEN) mm.c:907:d0 Error getting mfn 3a09c (pfn 55555555) from L1 entry 
> 000000003a09c023 for l1e_owner=0, pg_owner=0
>>> (XEN) mm.c:907:d0 Error getting mfn 3a09d (pfn 55555555) from L1 entry 
> 000000003a09d023 for l1e_owner=0, pg_owner=0
>>> (XEN) mm.c:907:d0 Error getting mfn 3a09e (pfn 55555555) from L1 entry 
> 000000003a09e023 for l1e_owner=0, pg_owner=0
>>> (XEN) mm.c:907:d0 Error getting mfn 3a09f (pfn 55555555) from L1 entry 
> 000000003a09f023 for l1e_owner=0, pg_owner=0
>>> (XEN) traps.c:2388:d0 Domain attempted WRMSR c0010004 from 
> 0x0000ab23d6d622da to 0x000000000000abcd.
>> Do they show up during bootup? As in do you see those _when_ you launch your 
> guests?
>> To figure out this particular issue you should try using 'console_to_ring' 
> (so that
>> dom0 output and Xen output are mingled togehter) and also post this under a 
> new subject
>> to not confuse this email thread.
> The messages show up during the initial dom0 boot, before any domUs are
> loaded. I've attached a second xl dmesg log which is similar to the
> first, but the numbers in the error messages are different.
> 
> The messages are hardware dependant as I don't get them on another
> system with different hardware configuration but with identical software.
> 
> The motherboard is a ASUS M2N68 AM PLUS, with 4GB of RAM. If I remove
> one of the sticks of ram to take it down to 2GB, the mm.c errors are no
> longer displayed, but I still get the traps.c message.

Would seem most likely to be I/O memory that doesn't get marked
properly when creating the page table entries, thus causing an
unintended phys->mach translation. If there are no kernel messages
associated with this, you will want to put some register/stack dumping
code in to determine what component in the kernel is causing this.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel