From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: HYP panic with 3.16-rc5, arm64 + 64k pages
Date: Fri, 18 Jul 2014 12:13:30 +0100 [thread overview]
Message-ID: <20140718111330.GC1818@arm.com> (raw)
In-Reply-To: <20140718084030.GA9548@arm.com>
On Fri, Jul 18, 2014 at 09:40:30AM +0100, Will Deacon wrote:
> On Thu, Jul 17, 2014 at 06:31:26PM +0100, Joel Schopp wrote:
> > Not a lot to go on there. If you get desperate you can configure FTRACE
> > and pass "ftrace=function ftrace_dump_on_oops" as additional additional
> > kernel command line arguments. If you get really desperate you can do
> > the same on the host. Just beware the output is really long.
>
> Cheers for the replies. It could be that I'm tickling something with kvmtool
> that qemu doesn't do, so I'll add some traces and try to figure out some more
> information later on today.
FWIW I just reproduced this issue but, this time, I didn't see a HYP panic.
The guest stopped at exactly the same point, but I then see a screaming
timer interrupt on the host. The weird part is that the screaming interrupt
is a PPI on physical CPU0, whilst the vcpus are affined to cores 4 and 5
(it's a Juno, so I've pinned the guest to the big cores).
I'll keep digging...
Will
prev parent reply other threads:[~2014-07-18 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 15:28 HYP panic with 3.16-rc5, arm64 + 64k pages Will Deacon
2014-07-17 17:31 ` Joel Schopp
2014-07-18 8:40 ` Will Deacon
2014-07-18 11:13 ` Will Deacon [this message]
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=20140718111330.GC1818@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).