From: Dirk Behme <dirk.behme@gmail.com>
To: xen-devel@lists.xenproject.org
Subject: xen/arm64: interrupt trouble porting to a new board
Date: Tue, 16 Feb 2016 17:50:48 +0100 [thread overview]
Message-ID: <56C35368.5090007@gmail.com> (raw)
Hi,
trying to bring up Xen on an ARM64 CA57 device (1 core atm) using a
recent Xen 4.7-unstable and Linux kernel 4.4.0+ I'm getting [1]. The
device tree configures arm,gic-400.
Regarding the <hang>, the Linux kernel boot messages are stopping
here. The debugger shows the system looping in xen/arch/arm/domain.c
idle_loop().
It's my impression that anything with the interrupts might be wrong,
which prevents the Linux kernel from further booting (?).
Talking about the interrupts, the log shows various
d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVERx
messages while the kernel is booting.
I'm not sure if both issues might be related (?).
Any idea?
Any hint where to look or debug?
Best regards
Dirk
[1]
...
Xen 4.7-unstable
...
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f1010000
(XEN) gic_cpu_addr=00000000f1020000
(XEN) gic_hyp_addr=00000000f1040000
(XEN) gic_vcpu_addr=00000000f1060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
...
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 288kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER40
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER44
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER48
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER52
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER56
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER60
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
[ 0.000000] Booting Linux on physical CPU 0x0
...
[ 0.173561] xen:grant_table: Grant tables using version 1 layout
[ 0.176538] Grant table initialized
[ 0.178321] xen:events: Using FIFO-based ABI
[ 0.180483] Xen: initializing cpu0
<hang>
reply other threads:[~2016-02-16 16:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56C35368.5090007@gmail.com \
--to=dirk.behme@gmail.com \
--cc=xen-devel@lists.xenproject.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).