qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hang in aio/multi/mutex/mcs
Date: Thu, 23 Feb 2017 19:48:52 +0000	[thread overview]
Message-ID: <87y3wwy9gb.fsf@linaro.org> (raw)
In-Reply-To: <CAJSP0QVjokCyvVtDcyWBhDqsWKwdNX6zyAo1uL9VmyzMfakS9A@mail.gmail.com>


Stefan Hajnoczi <stefanha@gmail.com> writes:

> Hi Paolo,
> Alex Benne reported that Travis CI is hanging in aio/multi/mutex/mcs:
>
> https://travis-ci.org/qemu/qemu/builds/203811867
>
> 0x00007fe9d680052d in nanosleep () from
> target:/lib/x86_64-linux-gnu/libpthread.so.0
> (gdb) info threads
>   Id   Target Id         Frame
> * 1    LWP 15116 "test-aio-multit" 0x00007fe9d680052d in nanosleep ()
> from target:/lib/x86_64-linux-gnu/libpthread.so.0
> (gdb) bt
> #0  0x00007fe9d680052d in nanosleep () from
> target:/lib/x86_64-linux-gnu/libpthread.so.0
> #1  0x00007fe9d74c6072 in g_usleep () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #2  0x000055b90b2e9dca in test_multi_fair_mutex (seconds=1, threads=5)
> at /tmp/qemu-test/src/tests/test-aio-multithread.c:363
> #3  0x00007fe9d74c365b in ?? () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #4  0x00007fe9d74c37d6 in ?? () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #5  0x00007fe9d74c37d6 in ?? () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #6  0x00007fe9d74c37d6 in ?? () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #7  0x00007fe9d74c3b2b in g_test_run_suite () from
> target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #8  0x000055b90b2e758c in main (argc=1, argv=0x7ffd65cb4928) at
> /tmp/qemu-test/src/tests/test-aio-multithread.c:462

To reproduce:

  make docker-test-quick@travis J=4 DEBUG=1
  /tmp/qemu-test/src/tests/docker/test-quick

This usually hangs for me. In another winder you can run:

  docker exec -it $CONTAINER_NAME bash

To get access to the filesystem and see the hung tasks.

If it doesn't trigger during this stage you may need to:

  cd /var/tmp/qemu-build
  ./tests/test-aio-multithread

Hope that helps the debugging ;-)

--
Alex Bennée

  reply	other threads:[~2017-02-23 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 18:29 [Qemu-devel] Hang in aio/multi/mutex/mcs Stefan Hajnoczi
2017-02-23 19:48 ` Alex Bennée [this message]
2017-02-24 16:22   ` Paolo Bonzini
2017-02-24 18:08     ` Alex Bennée

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=87y3wwy9gb.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).