Re: [Xen-devel] Unable to boot Xen 4.7-rc4 on HiKey

[Tamas K Lengyel <tamas.k.lengyel@xxxxxxxxx>]

On Thu, Jun 2, 2016 at 12:06 PM, Julien Grall <julien.grall@xxxxxxx> wrote:
> Hi Tamas,
>
> On 02/06/16 18:20, Tamas K Lengyel wrote:
>>
>> On Thu, Jun 2, 2016 at 11:14 AM, Tamas K Lengyel
>> <tamas.k.lengyel@xxxxxxxxx> wrote:
>>>
>>> On Thu, Jun 2, 2016 at 11:02 AM, Julien Grall <julien.grall@xxxxxxx>
>>> wrote:
>>
>> Xen 4.7.0-rc (c/s Mon May 23 12:07:20 2016 +0100 git:8478c94-dirty) EFI
>> loader
>> Using configuration file 'xen.cfg'
>> hi6220-hikey.dtb: 0x000000007acaf000-0x000000007acba6e0
>> Image: 0x0000000079fb9000-0x000000007aca1c00
>>   Xen 4.7.0-rc
>> (XEN) Xen version 4.7.0-rc (root@lan) (aarch64-linux-gnu-gcc
>> (Ubuntu/Linaro 5.3.1-14ubuntu2) 5.3.1 20160413) debug=n Wed Jun  1
>> 03:22:25 UTC 2016
>> (XEN) Latest ChangeSet: Mon May 23 12:07:20 2016 +0100 git:8478c94-dirty
>
>
> The tree seems to be dirty, what changes have you made into Xen?
>
> [...]
>
>> (XEN) Hypervisor Trap. HSR=0x96000006 EC=0x25 IL=1 Syndrome=0x6
>> (XEN) CPU0: Unexpected Trap: Hypervisor
>> (XEN) ----[ Xen-4.7.0-rc  arm64  debug=n  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) PC:     0000000000246494 xenmem_add_to_physmap_one+0x100/0x4e4
>
>
> Hmmm... have seen a such error yesterday on one of my platform and was not
> able to reproduce afterward :/.
>
> IIRC the PC was pointing to arch/arm/mm.c:1098. Can you confirm it is the
> same for you? You can use addr2line here.
>
> Can you reproduce it reliably? If so, could you provide your xen config,
> linux config, linux tree you are using?

I've recompiled Xen since with debug=y and the crash went away.. I'll
see if I can still reproduce it. Now that Xen is not crashing dom0
still did. I had to disable everything in the kernel related to
USB_DWC2 and recompile it, and finally everything boots!

Tamas

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel