From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Victor Kamensky <kamensky@cisco.com>,
Ian Arkver <ian.arkver.dev@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Need arm64/qemu help
Date: Sun, 11 Mar 2018 07:05:16 -0700 [thread overview]
Message-ID: <1520777116.10851.192.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1803101241080.24419@sjc-ads-6991.cisco.com>
Hi Victor,
On Sat, 2018-03-10 at 16:11 -0800, Victor Kamensky wrote:
> Any progress on the issue? In case if not, I am adding few Linaro
> guys
> who work on aarch64 qemu. Maybe they can give some insight.
>
> I was able to reproduce on my system and I
> and look at it under gdb. It seems that some strange aarch64
> percularity might be in play. Details inline, root cause is still
> not clear.
From the OE side we simply don't have people able to dig into this kind
of problem in detail unfortunately. I'm also travelling at the moment
which just complicates my own availability.
I am pleased you can replicate it and have been able to dig into it a
bit. My own theory was something like the timer interrupts stalling
since I've seen that problem on two other occasions recently on x86 and
ppc due to totally different issues but it sounds like you've ruled
that out.
At least from a replication standpoint it happens with a second of the
kernel boot so you don't need the rootfs and can likely script a fast
"brute force" of the issue (restart qemu until it hangs in boot).
I can confirm we continue to see the problem on our builds and it is
causing a real problem for us as we can't tell whether qemuarm64 is
really failing or just hanging :(
Any help in getting this figured out is much appreciated!
Cheers,
Richard
next prev parent reply other threads:[~2018-03-11 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 9:00 Need arm64/qemu help Richard Purdie
2018-03-03 10:51 ` Ian Arkver
2018-03-03 11:06 ` Richard Purdie
2018-03-03 11:13 ` Ian Arkver
2018-03-11 0:11 ` Victor Kamensky
2018-03-11 14:05 ` Richard Purdie [this message]
[not found] ` <CAFEAcA-d6-_tVRWKbZpVsQtece4fjuUqF+o+-m-AG4jPUHPY4g@mail.gmail.com>
2018-03-12 2:25 ` Victor Kamensky
2018-03-17 22:51 ` Victor Kamensky
[not found] ` <87a7v4kj5g.fsf@linaro.org>
2018-03-19 6:26 ` Victor Kamensky
[not found] ` <87605sjvk4.fsf@linaro.org>
2018-03-19 17:46 ` Victor Kamensky
[not found] ` <CAFEAcA8p9uO_7MXzkqyAnc-gifTHhmUgyRyE8X7hZnW=sbgQOg@mail.gmail.com>
2018-03-19 23:24 ` Victor Kamensky
[not found] ` <e15e3ca1-ee9e-1efa-2247-2789aac05091@linaro.org>
2018-03-20 2:22 ` Victor Kamensky
[not found] ` <874llbk1xc.fsf@linaro.org>
2018-03-20 2:14 ` Victor Kamensky
2018-03-03 18:21 ` Richard Purdie
2018-03-05 22:10 ` Ian Arkver
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=1520777116.10851.192.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.bennee@linaro.org \
--cc=ian.arkver.dev@gmail.com \
--cc=kamensky@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.maydell@linaro.org \
--cc=richard.henderson@linaro.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