From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARMv8: New board bring up hangs in kernel start?
Date: Tue, 29 Mar 2016 19:53:54 +0100 [thread overview]
Message-ID: <56FACF42.1020608@arm.com> (raw)
In-Reply-To: <56F2D158.804@gmail.com>
On 23/03/16 17:24, Dirk Behme wrote:
> Hi,
Hello Dirk,
Sorry for the late answer.
> trying to bring up Xen on a new ARMv8 64-bit Cortex A57 eval board, I
> get [1] and then its hanging there.
The logs look normal.
Do you know where the kernel get stuck? You can press CTRL-a 3 times to
get access to the Xen console and then press:
* 0 => dump Dom0 registers
* d => dump registers
> I'd guess that it hangs due to missing timer interrupt, maybe missing
> interrupts at all?
>
> Any hints how to debug this? Or where to look?
>
> It might be possible that the board's firmware (arm-trusted-firmware
> based) doesn't configure anything correctly. Firmware is running at EL3,
> Xen at EL2. The same kernel is running fine without Xen.
>
> Using a JTAG debugger I've put breakpoints into xen/arch/arm/time.c
> timer_interrupt() & vtimer_interrupt() but these don't seem to be called
> at all (?)
They should be called if the timer is configured correctly.
> Best regards
>
> Dirk
>
> [1]
[...]
> (XEN) Checking for initrd in /chosen
> (XEN) RAM: 0000000048000000 - 000000007fffffff
> (XEN)
> (XEN) MODULE[0]: 0000000048000000 - 00000000480058a2 Device Tree
> (XEN) MODULE[1]: 0000000048200000 - 0000000048c00000 Kernel
> (XEN)
> (XEN) Command line: console=dtuart dom0_mem=512M loglvl=all
> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
> (XEN) Update BOOTMOD_XEN from 0000000049000000-0000000049112e01 =>
> 000000007fe00000-000000007ff12e01
> (XEN) Domain heap initialised
> (XEN) Platform: ARMv8 Cortex A57 64-bit eval board
> (XEN) Taking dtuart configuration from /chosen/stdout-path
> (XEN) Looking for dtuart at "/soc/serial@e6e88000", options ""
> Xen 4.7-unstable
> (XEN) Xen version 4.7-unstable (dirk@build) (aarch64-poky-linux-gcc
> (Linaro GCC 4.9-2015.03) 4.9.3 20150311 (prerelease)) debug=y Mon Mar 21
> 09:15:03 CET 2016
> (XEN) Latest ChangeSet: Tue Feb 9 09:37:15 2016 +0100 git:b0a2893
I can't find this changeset in tree. Can you provide your baseline
commit and the list of patches you applied on top?
Also have you tried a newer version of Xen?
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-29 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 17:24 ARMv8: New board bring up hangs in kernel start? Dirk Behme
2016-03-23 18:41 ` Konrad Rzeszutek Wilk
2016-03-31 16:45 ` Stefano Stabellini
2016-03-29 18:53 ` Julien Grall [this message]
2016-03-31 17:41 ` Dirk Behme
2016-04-01 16:34 ` Julien Grall
2016-04-04 15:44 ` Dirk Behme
2016-04-06 10:48 ` Julien Grall
2016-04-16 17:39 ` Dirk Behme
2016-04-18 8:17 ` Julien Grall
2016-04-19 13:59 ` Dirk Behme
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=56FACF42.1020608@arm.com \
--to=julien.grall@arm.com \
--cc=dirk.behme@gmail.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).