From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Subject: Re: Panic on Seattle (resend)
Date: Tue, 30 Sep 2014 15:28:51 -0500
Message-ID: <542B1283.7070404@amd.com>
References: <542A5F07.2030600@amd.com> <1412073903.25650.7.camel@citrix.com>
	<542AC4EA.1090907@amd.com> <542ACAA8.8060608@linaro.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <542ACAA8.8060608@linaro.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Julien Grall <julien.grall@linaro.org>, Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>, "stefano.stabellini@eu.citrix.com" <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

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.

Thanks,

Suravee