From: Ian Campbell <Ian.Campbell@citrix.com>
To: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Cc: Julien Grall <julien.grall@linaro.org>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Panic on Seattle (resend)
Date: Wed, 1 Oct 2014 12:01:06 +0100 [thread overview]
Message-ID: <1412161266.4861.21.camel@citrix.com> (raw)
In-Reply-To: <542B1283.7070404@amd.com>
On Tue, 2014-09-30 at 15:28 -0500, Suravee Suthikulanit wrote:
> On 9/30/2014 10:22 AM, Julien Grall wrote:
> > Hi Suravee,
> >
> > On 30/09/2014 15:57, Suravee Suthikulpanit wrote:
> >>>> 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).
> >>
> >> Actually, I bisect it down to this commit ID causing it to break:
> >>
> >> commit 73b9bdfd2adab8ed0cea91d3e4470b0d1bf76591
> >> Author: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> >> Date: Fri Sep 12 16:39:46 2014 +0530
> >>
> >> xen/arm: Add virtual GICv3 support
> >>
> >> I am not sure at this point why. Here is the full Xen log.
> >>
> >> Loading Xen image..
> >> - UART enabled -
> >> - CPU 00000000 booting -
> >> - Current EL 00000008 -
> >> - Xen starting at EL2 -
> >> - Zero BSS -
> >> - Setting up control registers -
> >> - Turning on paging -
> >> - Ready -
> >> (XEN) Checking for initrd in /chosen
> >> (XEN) RAM: 0000008000000000 - 00000083ffffffff
> >> (XEN)
> >> (XEN) MODULE[0]: 000000801fffe000 - 000000801ffffc7d Device Tree
> >> (XEN) MODULE[1]: 0000008008800000 - 0000008009100890 Kernel
> >
> > [..]
> >
> >> (XEN) Placing Xen at 0x00000083ffe00000-0x0000008400000000
> >> (XEN) Update BOOTMOD_XEN from 0000008008700000-0000008008802d81 =>
> >> 00000083ffe00000-00000083fff02d81
> >
> > It looks like Xen is overlapping the beginning of the kernel in the memory.
> >
> > Xen: 0000008008700000-0000008008802d81
> > Kernel: 0000008008800000 - 0000008009100890
> >
> > Can you try to load Xen in another place in the memory?
> >
> > Regards,
> >
>
> (XEN) Checking for initrd in /chosen
> (XEN) RAM: 0000008000000000 - 00000083ffffffff
> (XEN)
> (XEN) MODULE[0]: 000000801fffe000 - 000000801ffffc7d Device Tree
> (XEN) MODULE[1]: 0000008008800000 - 0000008009100890 Kernel
> (XEN)
> (XEN) Command line: console=dtuart dtuart=serial0 noreboot sync_console
> (XEN) Placing Xen at 0x00000083ffe00000-0x0000008400000000
> (XEN) Update BOOTMOD_XEN from 0000008008600000-0000008008702d81 =>
> 00000083ffe00000-00000083fff02d81
>
> Yes, this now fixed once making sure Xen is loaded at least 2MB away
> from Image.
Great!
Anyone fancy coding up a check that none of the modules overlap each
other and/or Xen ;-)
Ian.
prev parent reply other threads:[~2014-10-01 11:01 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
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 [this message]
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=1412161266.4861.21.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).