Re: Panic on Seattle (resend)

[Julien Grall <julien.grall@linaro.org>]

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,

-- 
Julien Grall