xen-ia64-devel

[Top] [All Lists]

[Xen-ia64-devel] vcpu_translate: bad physical address: a000f00100cf0000

from [Matthew Chapman]

[Permanent Link][Original]

To:	xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-ia64-devel] vcpu_translate: bad physical address: a000f00100cf0000
From:	Matthew Chapman <matthewc@xxxxxxxxxxxxxxx>
Date:	Fri, 20 Jan 2006 00:33:05 +1100
Delivery-date:	Thu, 19 Jan 2006 13:40:41 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mutt/1.5.9i

The current Xen/ia64 tree doesn't work for me, Dom0 dies here:

Memory: 491056k/523264k available (11335k code, 31600k reserved, 4831k data, 
304k init)
(XEN) vcpu_translate: bad physical address: a000f00100cf0000 @ a0000001000080d0 
(kr7=000000000ccec000)
[machine check]

The erroneous fault is in vhpt_miss while handling a region 5
miss (the first, from ia64_patch_gate).  The address comes from:

  LOAD_PHYSICAL(p6, r19, swapper_pg_dir)

which is a movl which is patched into a physical address by
ia64_patch_vtop.

The unpatched value is 0xa000000100cf0000, and it should have
been patched to 0xccf0000.  Having added some debug output to
ia64_patch_imm64, it seems that tpa produces the right value, and
it tries to patch it.

However, something obviously goes wrong, since the address above
is neither the unpatched address nor the intended physical
address.

Anyone seen this before?

Matt


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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-ia64-devel] vcpu_translate: bad physical address: a000f00100cf0000, Matthew Chapman <= [PATCH] Re: [Xen-ia64-devel] vcpu_translate: bad physical address: a000f00100cf0000, Matthew Chapman

Previous by Date:	[Xen-ia64-devel] ramdisk generated by xm-test, Matsumoto
Next by Date:	RE: [Xen-ia64-devel] vcpu_translate: bad physical address:a000f00100cf0000, Magenheimer, Dan (HP Labs Fort Collins)
Previous by Thread:	[Xen-ia64-devel] ramdisk generated by xm-test, Matsumoto
Next by Thread:	[PATCH] Re: [Xen-ia64-devel] vcpu_translate: bad physical address: a000f00100cf0000, Matthew Chapman
Indexes:	[Date] [Thread] [Top] [All Lists]