From: Marek Vasut <marex@denx.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <huth@tuxfamily.org>, Chris Wulff <crwulff@gmail.com>
Cc: Richard Henderson <rth@twiddle.net>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-nios2 hangs when emulator is quit
Date: Tue, 10 Oct 2017 18:23:49 +0200 [thread overview]
Message-ID: <d32cdc97-8efc-2103-26b5-f9c80b966e26@denx.de> (raw)
In-Reply-To: <fdfdf890-bfa0-eadf-c1f5-bf4e9e1c23e5@redhat.com>
On 10/10/2017 05:19 PM, Paolo Bonzini wrote:
> On 10/10/2017 10:58, Marek Vasut wrote:
>>> #0 0x00007ffff7931945 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
>>> #1 0x00005555557cf9c5 in qemu_cond_wait (cond=cond@entry=0x555555b5f9c0 <qemu_pause_cond>, mutex=mutex@entry=0x555555b5fa40 <qemu_global_mutex>) at util/qemu-thread-posix.c:161
>>> #2 0x0000555555606ee8 in pause_all_vcpus () at cpus.c:1620
>>> #3 0x00005555555cc43a in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>)
>>> at vl.c:4906
>>>
>>> Looks like the CPU does not get stopped right? Unfortunately, I've got no
>>> good clue how to debug that further right now...
>> I'd look at pause_all_vcpus() and check why it is stuck.
>> I'm a bit overloaded at the moment, so I don't have time to dig in it.
>>
>
> It's actually the CPU thread that is stuck because the
> start-of-translation-block test is wrong and never succeeds:
>
> 0x7fd715fff0c0: mov -0x14(%rsp),%ebp
> 0x7fd715fff0c4: test %ebp,%ebp
> 0x7fd715fff0c6: jl 0x7fd715fff0e4
>
> It should be using %r14, not %rsp. I've sent a patch.
Oh nice, thank you :)
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-10-10 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:20 [Qemu-devel] qemu-system-nios2 hangs when emulator is quit Thomas Huth
2017-10-10 7:57 ` Marek Vasut
2017-10-10 8:15 ` Thomas Huth
2017-10-10 8:58 ` Marek Vasut
2017-10-10 15:19 ` Paolo Bonzini
2017-10-10 16:23 ` Marek Vasut [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=d32cdc97-8efc-2103-26b5-f9c80b966e26@denx.de \
--to=marex@denx.de \
--cc=crwulff@gmail.com \
--cc=huth@tuxfamily.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).