From: Ian Campbell <Ian.Campbell@citrix.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Cc: Julien Grall <julien.grall@linaro.org>,
xen-devel <xen-devel@lists.xen.org>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>
Subject: Re: Panic on Seattle (resend)
Date: Tue, 30 Sep 2014 11:45:03 +0100 [thread overview]
Message-ID: <1412073903.25650.7.camel@citrix.com> (raw)
In-Reply-To: <542A5F07.2030600@amd.com>
On Tue, 2014-09-30 at 02:43 -0500, Suravee Suthikulpanit wrote:
> Hi All,
>
> I have been trying to boot the latest Xen code on Seattle (while I am
> getting the patch ready to be sent out), and I ran into the following issue.
>
> .....
> (XEN) Brought up 6 CPUs
> (XEN) CPU 5 booted.
> (XEN) P2M: 44-bit IPA with 44-bit PA
> (XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading kernel from boot module @ 0000008008800000
> (XEN) elf_init: not an ELF binary
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Could not set up DOM0 guest OS
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
>
> I have not tracked down to a particular commit ID. But do you guys see
> anything suspicious with the error message?
The elf_init thing is suspicious, it suggests Xen hasn't properly
figured out the type of your kernel image. Is it a regular bare arm64
Image (from arch/arm64/boot/Image)? You can't boot the vmlinux from the
top level directly (AFAIK).
> My understanding is with 4-level page, it requires 4K page and 48 bits
> PA. However, the message above showing 44-bit PA. Is this intentional?
The 44 comes from ID_AA64MMFR0_EL1.PARange.
4-levels are required for anything above 40-bits, so 44-bit PA also
needs 4-levels. This comes from things like tables D4-5 and D4-10 in the
ARMv8 ARM, which give the T0SZ range and maximum number of
levels/concatenation for various PAsizes.
Ian.
next prev parent reply other threads:[~2014-09-30 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:43 Panic on Seattle (resend) Suravee Suthikulpanit
2014-09-30 10:45 ` Ian Campbell [this message]
2014-09-30 14:57 ` Suravee Suthikulpanit
2014-09-30 15:07 ` Suravee Suthikulpanit
2014-09-30 15:22 ` Julien Grall
2014-09-30 20:28 ` Suravee Suthikulanit
2014-10-01 11:01 ` Ian Campbell
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=1412073903.25650.7.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.