qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Gabriel Kerneis <gabriel@kerneis.info>,
	qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] coroutine: add ./configure --disable-coroutine-pool
Date: Wed, 2 Oct 2013 10:54:29 +0200	[thread overview]
Message-ID: <20131002085429.GE2142@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <524AFC06.1060906@weilnetz.de>

On Tue, Oct 01, 2013 at 06:44:54PM +0200, Stefan Weil wrote:
> Am 01.10.2013 09:29, schrieb Gabriel Kerneis:
> > On Tue, Oct 01, 2013 at 07:51:24AM +0200, Stefan Weil wrote:
> >> $ wine i386-softmmu/qemu-system-i386 -L pc-bios -cdrom /var/tmp/mini.iso
> >> -sdl # or -vnc :1
> >>
> >> => Assertion in qemu-coroutine-lock.c:99.
> > Could you please provide the backtrace for this?  I am curious which of the uses
> > of qemu_co_queue_restart_all() fails.  I wonder if it is a bug in the
> > implementation of qemu_in_coroutine() on your platform, or really a rare
> > interleaving which exhibits a bug in the logic of coroutine functions.
> >
> 
> Here is a GDB protocol. Build environment:
> 
> Windows 7 (64 bit) host
> MinGW toolchain (not MinGW-w64 which I usually prefer)
> ./configure && make
> 
> $ gdb --args bin/ndebug/mingw32/i386-softmmu/qemu-system-i386 -L pc-bios
> -cdrom mini.iso
> GNU gdb (GDB) 7.5
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-mingw32".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from
> c:\home\stefan\src\qemu\qemu.org\qemu\bin\ndebug\mingw32\i386-softmmu\qemu-system-i386.exe...done.
> (gdb) b abort
> Breakpoint 1 at 0x6b0070
> (gdb) r
> Starting program:
> c:\home\stefan\src\qemu\qemu.org\qemu\bin\ndebug\mingw32\i386-softmmu\qemu-system-i386.exe
> -L pc-bios -cdrom mini.iso
> [New Thread 4120.0x19c4]
> [New Thread 4120.0x1724]
> [New Thread 4120.0x1a98]
> [New Thread 4120.0x1854]
> [New Thread 4120.0x1bf8]
> VNC server running on `::1:5900'
> Assertion failed: qemu_in_coroutine(), file
> c:/home/stefan/src/qemu/qemu.org/qemu/qemu-coroutine-lock.c, line 99
> [Switching to Thread 4120.0x1a98]
> 
> Breakpoint 1, 0x76118e76 in msvcrt!abort ()
>    from C:\Windows\syswow64\msvcrt.dll
> (gdb) i s
> #0  0x76118e76 in msvcrt!abort () from C:\Windows\syswow64\msvcrt.dll
> #1  0x7611680c in msvcrt!_assert () from C:\Windows\syswow64\msvcrt.dll
> #2  0x00518f2d in qemu_co_queue_restart_all (queue=queue@entry=0x6d3fe90)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/qemu-coroutine-lock.c:99
> #3  0x0040ee81 in tracked_request_end (req=0x6d3fe6c)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/block.c:1963
> #4  bdrv_co_do_readv (bs=0x3057658, sector_num=<optimized out>,
> nb_sectors=4,
>     qiov=0x733f9d0, flags=<optimized out>)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/block.c:2675
> #5  0x0040ee52 in bdrv_co_do_readv (bs=0x3055c10, sector_num=<optimized
> out>,
>     nb_sectors=4, qiov=0x733f9d0, flags=<optimized out>)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/block.c:2645
> #6  0x0040ffbc in bdrv_rw_co_entry (opaque=0x733f968)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/block.c:2276
> #7  0x00441be8 in coroutine_trampoline (co_=0x3058958)
>     at c:/home/stefan/src/qemu/qemu.org/qemu/coroutine-win32.c:57
> #8  0x7549bfa2 in KERNEL32!GetQueuedCompletionStatus ()
>    from C:\Windows\syswow64\kernel32.dll
> #9  0x03058958 in ?? ()
> #10 0x7549bf5a in KERNEL32!GetQueuedCompletionStatus ()
>    from C:\Windows\syswow64\kernel32.dll
> #11 0x014feff0 in ?? ()

This is an interesting backtrace.  The 'current' thread-local variable
from coroutine-win32.c is NULL or doesn't have a caller assigned.

Please post 'thread apply all bt' so we can identify the other threads.

Stefan

  reply	other threads:[~2013-10-02  8:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 14:42 [Qemu-devel] [PATCH] coroutine: add ./configure --disable-coroutine-pool Stefan Hajnoczi
2013-09-11 14:56 ` Gabriel Kerneis
2013-09-11 15:24 ` Kevin Wolf
2013-09-11 15:32   ` Gabriel Kerneis
2013-09-11 15:38     ` Kevin Wolf
2013-09-12  8:42       ` Stefan Hajnoczi
2013-09-27  5:20 ` Stefan Weil
2013-09-27  9:11   ` Stefan Hajnoczi
2013-09-27 16:49     ` Stefan Weil
2013-09-30  9:06       ` Stefan Hajnoczi
2013-10-01  5:51         ` Stefan Weil
2013-10-01  7:29           ` Gabriel Kerneis
2013-10-01 16:44             ` Stefan Weil
2013-10-02  8:54               ` Stefan Hajnoczi [this message]
2013-10-02 21:15                 ` Stefan Weil
2013-10-04  7:30                   ` Stefan Hajnoczi
2013-10-01  7:21         ` Paolo Bonzini

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=20131002085429.GE2142@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=gabriel@kerneis.info \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).