From: John Snow <jsnow@redhat.com>
To: Like Xu <like.xu@linux.intel.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"Thomas Huth \(S390-ccw/CHRP/qtest/GitLab\)" <thuth@redhat.com>,
vsementsov@virtuozzo.com,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [RESEND][BUG FIX HELP] QEMU main thread endlessly hangs in __ppoll()
Date: Fri, 5 Mar 2021 11:53:55 -0500 [thread overview]
Message-ID: <e6cdfded-6727-2f73-358f-a9c019ca29f8@redhat.com> (raw)
In-Reply-To: <624a6256-a735-6475-8831-b4c85f225c94@linux.intel.com>
On 3/4/21 10:08 PM, Like Xu wrote:
> Hi John,
>
> Thanks for your comment.
>
> On 2021/3/5 7:53, John Snow wrote:
>> On 2/28/21 9:39 PM, Like Xu wrote:
>>> Hi Genius,
>>>
>>> I am a user of QEMU v4.2.0 and stuck in an interesting bug, which may
>>> still exist in the mainline.
>>> Thanks in advance to heroes who can take a look and share understanding.
>>>
>>
>> Do you have a test case that reproduces on 5.2? It'd be nice to know
>> if it was still a problem in the latest source tree or not.
>
> We narrowed down the source of the bug, which basically came from
> the following qmp usage:
>
> {'execute': 'human-monitor-command', 'arguments':{ 'command-line':
> 'drive_del replication0' } }
>
> One of the test cases is the COLO usage (docs/colo-proxy.txt).
>
> This issue is sporadic,the probability may be 1/15 for a io-heavy guest.
>
> I believe it's reproducible on 5.2 and the latest tree.
>
Can you please test and confirm that this is the case, and then file a
bug report on the LP: https://launchpad.net/qemu and include:
- The exact commit you used (current origin/master debug build would be
the most ideal.)
- Which QEMU binary you are using (qemu-system-x86_64?)
- The shortest command line you are aware of that reproduces the problem
- The host OS and kernel version
- An updated call trace
- Any relevant commands issued prior to the one that caused the hang; or
detailed reproduction steps if possible.
Thanks,
--js
prev parent reply other threads:[~2021-03-05 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 2:39 [RESEND][BUG FIX HELP] QEMU main thread endlessly hangs in __ppoll() Like Xu
2021-03-04 23:53 ` John Snow
2021-03-05 3:08 ` Like Xu
2021-03-05 16:53 ` John Snow [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=e6cdfded-6727-2f73-358f-a9c019ca29f8@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=like.xu@linux.intel.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vsementsov@virtuozzo.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).