From: Rik van Riel <riel@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: invalid PTE for xen_start-info ?
Date: Tue, 03 Oct 2006 14:06:41 -0400 [thread overview]
Message-ID: <4522A6B1.8000304@redhat.com> (raw)
In-Reply-To: <C147FB18.1F5D%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> Please beat up on this release candidate and post bug reports on any
> outstanding issues. We are getting close to 3.0.3-0 final release!
I am seeing some suspicious output from the xen_start_info
pte address at startup. This is with the 2.6.9 Xen code,
which is mostly based off an older code base, but I notice
that mfn_to_pfn() in the current codebase seems to have a
workaround for this bug.
Started domain crumble
xen_start_info @ffffffff8087c000
shared @m0000fc3000 @ffffffff80107000=@ffffffffff5fd000 [0x802]
xen_start_info: @ffffffff8087c000
cr3 0000000000101000 pml4p ffffffff80101ff8
pml4e 0000000000103067 (real 0000000035e09067) pgdp ffffff8000103ff0
pgde 0000000000105067 (real 0000000035e07067) pmdp ffffff8000105020
pmde 0000000000886067 (real 0000000035006067) ptep ffffff80008863e0
pte 0000000019800027 (real 0010000035010027)
That last PTE value does not look like a valid x86-64 PTE
value to me. That high bit is not the NX bit, nor is it
within the physical address range of the system in question.
What's going on here?
Is this a bug you would like a fix for?
--
All Rights Reversed
next prev parent reply other threads:[~2006-10-03 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 10:33 Xen 3.0.3 rc2 available Keir Fraser
2006-10-03 18:06 ` Rik van Riel [this message]
2006-10-04 8:08 ` invalid PTE for xen_start-info ? Keir Fraser
2006-10-04 13:47 ` Rik van Riel
2006-10-04 14:16 ` Keir Fraser
2006-10-04 15:06 ` Rik van Riel
2006-10-04 15:10 ` Keir Fraser
2006-10-03 18:17 ` xen-3.0.3-testing-install-x86_32 dom0 boot failure Richard Miller
2006-10-04 13:46 ` [PATCH] redundant ampersand before array name in __RING_SIZE macro Richard Miller
2006-10-06 20:47 ` Xen 3.0.3 rc2 available Nick Craig-Wood
2006-10-06 20:55 ` Anthony Liguori
2006-10-09 8:46 ` Nick Craig-Wood
2006-10-06 22:44 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4522A6B1.8000304@redhat.com \
--to=riel@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.