All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fernando Casas Schössow" <casasfernando@outlook.com>
To: "Fernando Casas Schössow" <casasfernando@hotmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Jeff Cody <jcody@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests)
Date: Fri, 16 Nov 2018 11:04:37 +0000	[thread overview]
Message-ID: <AM0PR06MB52990C51EA2E76CFC9D9D8BDA4DD0@AM0PR06MB5299.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <AM6PR10MB2247D63F532AE33155BA57EFB7F80@AM6PR10MB2247.EURPRD10.PROD.OUTLOOK.C OM>

Hi again,

I hit another occurrence of this issue and collected the qemy dump as well. So at the moment I have two qemu dumps for this issue happening on two different guests.
I wish I know how to analyze them myself but is not the case so if anyone in the list is willing to take a look I'm more than willing to share them.

Thanks in advance.

Fernando

On jue, oct 18, 2018 at 3:40 PM, Fernando Casas Schössow <casasfernando@hotmail.com> wrote:
Hi Kevin,

Not at the moment. This is a production system and pretty much up to date but can't upgrade to 3.0 yet.
If the dump can be of any use, I can upload it somewhere for analysis.

BR,

Fernando

On jue, oct 18, 2018 at 2:38 PM, Kevin Wolf <kwolf@redhat.com> wrote:
Hi Fernando, Am 18.10.2018 um 14:25 hat Fernando Casas Schössow geschrieben:
I hope this email finds you well and I apologize in advance for resurrecting this thread. I'm currently running on qemu 2.12.1 and I'm still having this issue every few days but now I managed to get a core dump generated (without including the guest memory). Would you take a look at the dump? Please let me know how do you prefer me to share it. The file is around 290MB as is but I can try to compress it.
would it be possible for you to test whether the bug still exists in QEMU 3.0? There were a few fixes related to request draining in that release, so maybe it's already solved now. Kevin

      parent reply	other threads:[~2018-11-16 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 10:18 [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests) Fernando Casas Schössow
2017-12-11 11:56 ` Stefan Hajnoczi
2017-12-11 13:42   ` Fernando Casas Schössow
2017-12-13 11:23     ` Stefan Hajnoczi
2017-12-13 15:33       ` Fernando Casas Schössow
2018-01-29 16:01         ` Stefan Hajnoczi
2018-10-18 12:25           ` Fernando Casas Schössow
2018-10-18 12:38             ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2018-10-18 13:40               ` Fernando Casas Schössow
     [not found]                 ` <AM6PR10MB2247D63F532AE33155BA57EFB7F80@AM6PR10MB2247.EURPRD10.PROD.OUTLOOK.C OM>
2018-11-16 11:04                   ` Fernando Casas Schössow [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=AM0PR06MB52990C51EA2E76CFC9D9D8BDA4DD0@AM0PR06MB5299.eurprd06.prod.outlook.com \
    --to=casasfernando@outlook.com \
    --cc=casasfernando@hotmail.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.