From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Coiby Xu <Coiby.Xu@gmail.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: Re: intermittent hang in qos-test for qemu-system-i386 on 32-bit arm host
Date: Fri, 16 Jul 2021 16:31:49 +0200 [thread overview]
Message-ID: <YPGYVeuzp3lj2yJk@redhat.com> (raw)
In-Reply-To: <CAFEAcA9PSZaHkV-qL9jvXX_MFKwYJJTSQ4FjQJfwyRi7GvJvWg@mail.gmail.com>
Am 11.07.2021 um 17:53 hat Peter Maydell geschrieben:
> On Sat, 10 Jul 2021 at 14:30, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > I've noticed recently that intermittently 'make check' will hang on
> > my aarch32 test system (really an aarch64 box with an aarch32 chroot).
> >
> > I think from grep that this must be the vhost-user-blk test.
>
> I've also now seen this on qemu-system-i386 guest x86-64 Linux host:
Your two stack traces look very different to me, the common thing is
just that one process requests something and the other seems to have
ignored it and is just idle.
In the first stack trace, it was the qtest sending the very first
command ('endianness') over the qtest socket and QEMU seemed to ignore
it. In the second stack trace, it is the vhost-user-blk realize() code
in QEMU sending a request to the export in qemu-storage-daemon and never
getting an answer.
If this is the same bug, it looks to me as if it's something with the
event notification in the main loop? Can we check if there would
actually be an event pending in the apparently idle process if ppoll()
returned?
Kevin
next prev parent reply other threads:[~2021-07-16 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 13:30 intermittent hang in qos-test for qemu-system-i386 on 32-bit arm host Peter Maydell
2021-07-11 12:08 ` Coiby Xu
2021-07-11 12:16 ` Peter Maydell
2021-07-11 13:23 ` Richard Henderson
2021-07-11 14:21 ` Peter Maydell
2021-07-11 14:27 ` Richard Henderson
2021-07-11 22:19 ` Coiby Xu
2021-07-11 15:53 ` Peter Maydell
2021-07-11 22:20 ` Coiby Xu
2021-07-11 22:50 ` Coiby Xu
2021-07-12 9:39 ` Peter Maydell
2021-07-16 12:30 ` Coiby Xu
2021-07-16 14:31 ` Kevin Wolf [this message]
2021-07-22 8:45 ` Claudio Fontana
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=YPGYVeuzp3lj2yJk@redhat.com \
--to=kwolf@redhat.com \
--cc=Coiby.Xu@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
/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).