From: Max Reitz <mreitz@redhat.com>
To: Qemu-block <qemu-block@nongnu.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] Intermittent failure of iotest 203
Date: Fri, 23 Feb 2018 14:03:15 +0100 [thread overview]
Message-ID: <60d1e2ab-c3a4-cae2-b810-5e46dc124b0b@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Hi,
iotest 203 relatively often fails for me, at least when run in parallel.
When I run the following concurrently on four shells:
$ while TEST_DIR=/tmp/t1 ./check -T -qcow2 203; do; done
$ while TEST_DIR=/tmp/t2 ./check -T -qcow2 203; do; done
$ while TEST_DIR=/tmp/t3 ./check -T -qcow2 203; do; done
$ while TEST_DIR=/tmp/t4 ./check -T -qcow2 203; do; done
Very quickly (like under ten iterations), at least one of those starts
to hang and then fails because of a timeout in vm.get_qmp_event().
Before digging deeper into the ppoll() dungeon* myself, I decided to
report this so I wouldn't have to. :-)
*Backtrace:
(gdb) bt
#0 0x00007f354137b4d6 in ppoll () at /lib64/libc.so.6
#1 0x000055b659144299 in ppoll (__ss=0x0, __timeout=0x7ffe4eaca230,
__nfds=<optimized out>, __fds=<optimized out>) at
/usr/include/bits/poll2.h:77
#2 0x000055b659144299 in qemu_poll_ns (fds=<optimized out>,
nfds=<optimized out>, timeout=timeout@entry=39512999619000) at
util/qemu-timer.c:334
#3 0x000055b6591450a3 in os_host_main_loop_wait (timeout=<optimized
out>) at util/main-loop.c:255
#4 0x000055b6591450a3 in main_loop_wait (nonblocking=<optimized out>)
at util/main-loop.c:515
#5 0x000055b658d4a253 in main_loop () at vl.c:1933
#6 0x000055b658d4a253 in main (argc=<optimized out>, argv=<optimized
out>, envp=<optimized out>) at vl.c:4757
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next reply other threads:[~2018-02-23 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 13:03 Max Reitz [this message]
2018-03-05 15:44 ` [Qemu-devel] Intermittent failure of iotest 203 Stefan Hajnoczi
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=60d1e2ab-c3a4-cae2-b810-5e46dc124b0b@redhat.com \
--to=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).