From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: d0 Error pfn 100
Date: Thu, 24 May 2007 13:28:33 +0100
Message-ID: <C27B4381.F720%keir@xensource.com>
References: <200705241421.20342.Christoph.Egger@amd.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <200705241421.20342.Christoph.Egger@amd.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

This is a harmless message printed at loglevel XENLOG_INFO. Not much we can
do about it (apart from remove the message or reduce its loglevel further).
It is caused by yast doing some kind of scan of low memory, which we
disallow above physical address 1MB (there'll be nothing of interest at 1MB
or above anyway).

 -- Keir


On 24/5/07 13:21, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> 
> Hi!
> 
> I see these messages from the xen-kernel:
> 
> (XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100:
> rd=ffff8300df05c100, od=0000000000000000, caf=00000000, taf=0000000000000000
> (XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry
> 8000000000100125 for dom32753
> (XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100:
> rd=ffff8300df05c100, od=0000000000000000, caf=00000000, taf=0000000000000000
> (XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry
> 8000000000100125 for dom32753
> 
> Xen does not crash, Dom0 continues to run.
> 
> System configuration:
> 
> x86_64 debug xen-kernel, x86_64 linux-2.6.18 dom0 kernel built from xen tree,
> OpenSuSE 10.2 distribution as Dom0.
> 
> Steps to reproduce:
> 
> Launch yast, select "Network devices" and "Network card".
> yast now reads config entries. If you are on a serial console where screen
> refreshes are slow enough, you should see that xen prints something.
> Exit yast without changing anything. Back on command line run "xm dmesg".
> There you can see the above xen messages.
> 
> This is repeatable. Doing this multiple times without reboot, you can always
> see the same message even with the same numbers.
> 
> 
> Question:
> 
> Can anyone else on this list reproduce this?
> 
> 
> Christoph
>