xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.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 09:57:46 -0500	[thread overview]
Message-ID: <542AC4EA.1090907@amd.com> (raw)
In-Reply-To: <1412073903.25650.7.camel@citrix.com>



On 09/30/2014 05:45 AM, Ian Campbell wrote:
> 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).

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)
(XEN) Command line: console=dtuart dtuart=serial0 noreboot sync_console
(XEN) Placing Xen at 0x00000083ffe00000-0x0000008400000000
(XEN) Update BOOTMOD_XEN from 0000008008700000-0000008008802d81 => 
00000083ffe00000-00000083fff02d81
(XEN) Domain heap initialised
(XEN) Looking for UART console serial0
  Xen 4.5-unstable
(XEN) Xen version 4.5-unstable (ssuthiku@) (aarch64-linux-gnu-gcc 
(crosstool-NG linaro-1.13.1-4.8-2014.01 - Linaro GCC 2013.11) 4.8.3 
20140106 (prerelease)) debug=y Tue Sep 30 09:41:14 CDT 2014
(XEN) Latest ChangeSet: Mon Aug 25 22:31:06 2014 -0500 git:ecf3789-dirty
(XEN) Console output is synchronous.
(XEN) Processor: 410fd070: "ARM Limited", variant: 0x0, part 0xd07, rev 0x0
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001124 0000000000000000
(XEN)   ISA Features:  0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10101105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Platform: SEATTLE
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 187500 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000e1110000
(XEN)         gic_cpu_addr=00000000e112f000
(XEN)         gic_hyp_addr=00000000e1140000
(XEN)         gic_vcpu_addr=00000000e1160000
(XEN)         gic_maintenance_irq=24
(XEN) GICv2: 448 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) I/O virtualisation disabled
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
- CPU 00000201 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000200 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000101 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
- CPU 00000100 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 4 booted.
(XEN) Bringing up CPU5
- CPU 00000001 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Brought up 6 CPUs
(XEN) CPU 5 booted.
(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)

Suravee

  reply	other threads:[~2014-09-30 14:57 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 [this message]
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=542AC4EA.1090907@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=Ian.Campbell@citrix.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 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).