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-ia64-devel

Re: [Xen-ia64-devel] [RFC] Enable dom0 to start X

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-ia64-devel] [RFC] Enable dom0 to start X
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Mon, 24 Jul 2006 14:36:22 +0200
Delivery-date: Mon, 24 Jul 2006 05:32:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <22C6AF1BC67B25takebe_akio@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <22C6AF1BC67B25takebe_akio@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Lundi 24 Juillet 2006 14:22, Akio Takebe a écrit :
> Hi, all
>
> I'm debugging Xwindow system of dom0.
[...]
> At the results, I could startx, but not completely.
> I found X run while using 100% CPU with top command.
> The following messages were shown at that time.
>
> (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=>
> 0x20000000)
> (XEN) lookup_domain_mpa: d 0xf000000004288080 id 0 current
> 0xf000000004260000 id 0
>
> I think this 0xf000000004288080 is I/O page to be used by X.
> (this 0xf000000004288080 is also not shown in memmap of Tiger4)
> The I/O page seem to be not allocated.
> How/When should xen allocate this page?
Hi,

you are misreading the message.
The bad mpa is 0xfbfd0738!
0xf000000004288080 is the address of struct domain, which is a valid virtual 
address.

Tristan.

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

<Prev in Thread] Current Thread [Next in Thread>