From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"pve-devel@pve.proxmox.com" <pve-devel@pve.proxmox.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] segfault in aio_bh_poll async.c:80 WAS: Re: kvm process disappears
Date: Tue, 14 May 2013 17:11:56 +0200 [thread overview]
Message-ID: <5192543C.4010305@profihost.ag> (raw)
In-Reply-To: <CAJSP0QVAUehdHYuuT3x3omesiSa+N7tTnZxHzict2T-aLJfKmA@mail.gmail.com>
Am 14.05.2013 17:05, schrieb Stefan Hajnoczi:
> On Tue, May 14, 2013 at 4:29 PM, Stefan Priebe - Profihost AG
> <s.priebe@profihost.ag> wrote:
>> Am 10.05.2013 13:09, schrieb Stefan Hajnoczi:
>>> On Fri, May 10, 2013 at 11:07 AM, Stefan Priebe - Profihost AG
>>> <s.priebe@profihost.ag> wrote:
>>>> Am 10.05.2013 09:42, schrieb Stefan Hajnoczi:
>>>>> On Fri, May 10, 2013 at 08:12:39AM +0200, Stefan Priebe - Profihost AG wrote:
>>>>> 3. Either use gdb or an LD_PRELOAD library that catches exit(3) and
>>>>> _exit(2) and dumps core using abort(3). Make sure core dumps are
>>>>> enabled.
>>
>> This time i had a segfault Qemu 1.4.1 plus
>> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=dc7588c1eb3008bda53dde1d6b890cd299758155.
>>
>> aio_bh_poll async.c:80
>>
>> Code...
>>
>> for (bh = ctx->first_bh; bh; bh = next) {
>> next = bh->next;
>> if (!bh->deleted && bh->scheduled) {
>> bh->scheduled = 0;
>> if (!bh->idle)
>> ret = 1;
>> bh->idle = 0;
>> bh->cb(bh->opaque);
>> }
>> }
>>
>> ctx->walking_bh--;
>>
>> /* remove deleted bhs */
>> if (!ctx->walking_bh) {
>> bhp = &ctx->first_bh;
>> while (*bhp) {
>> bh = *bhp;
>> ===== THIS IS THE SEGFAULT LINE ===== if (bh->deleted) {
>> *bhp = bh->next;
>> g_free(bh);
>> } else {
>> bhp = &bh->next;
>> }
>> }
>> }
>>
>> return ret;
>
> Interesting crash. Do you have the output of "thread apply all bt"?
>
> I would try looking at the AioContext using "p *ctx", and print out
> the ctx->first_bh linked list.
Hi,
as i can't reproduce no ;-( i just saw the kernel segfault message and
used addr2line and a qemu dbg package to get the code line.
Stefan
next prev parent reply other threads:[~2013-05-14 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 6:12 [Qemu-devel] kvm process disappears Stefan Priebe - Profihost AG
2013-05-10 7:15 ` [Qemu-devel] [pve-devel] " Alexandre DERUMIER
2013-05-10 7:20 ` Alexandre DERUMIER
2013-05-10 7:22 ` Stefan Priebe - Profihost AG
2013-05-10 7:28 ` Alexandre DERUMIER
2013-05-10 9:06 ` Stefan Priebe - Profihost AG
2013-05-10 7:42 ` [Qemu-devel] " Stefan Hajnoczi
2013-05-10 9:07 ` Stefan Priebe - Profihost AG
2013-05-10 11:09 ` Stefan Hajnoczi
2013-05-14 14:29 ` [Qemu-devel] segfault in aio_bh_poll async.c:80 WAS: " Stefan Priebe - Profihost AG
2013-05-14 15:05 ` Stefan Hajnoczi
2013-05-14 15:11 ` Stefan Priebe - Profihost AG [this message]
2013-05-22 6:26 ` Stefan Priebe - Profihost AG
2013-05-22 8:41 ` Paolo Bonzini
2013-05-22 12:24 ` Stefan Priebe - Profihost AG
2013-05-23 10:09 ` Paolo Bonzini
2013-05-23 19:22 ` Stefan Priebe
2013-05-27 21:09 ` [Qemu-devel] " Stefan Priebe
2013-05-28 8:06 ` 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=5192543C.4010305@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pve-devel@pve.proxmox.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 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.