Re: [Qemu-devel] [Bug 1498144] [NEW] Failure booting hurd with qemu-system-i386 on ARM

[Laszlo Ersek <lersek@redhat.com>]

On 09/21/15 21:04, PeteVine wrote:
> Public bug reported:
> 
> Trying to boot debian-hurd-20150320.img ends with:
> 
> qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all:
> Assertion `qemu_in_coroutine()' failed.
> 
> Program received signal SIGABRT, Aborted.
> __libc_do_syscall ()
>     at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
> 44      ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory.
> (gdb) bt
> #0  __libc_do_syscall ()
>     at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
> #1  0xb6ef8f0e in __GI_raise (sig=sig@entry=6)
>     at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #2  0xb6efb766 in __GI_abort () at abort.c:89
> #3  0xb6ef4150 in __assert_fail_base (
>     fmt=0x1 <error: Cannot access memory at address 0x1>, 
>     assertion=0x7f89a234 "qemu_in_coroutine()", assertion@entry=0x0, 
>     file=0x7f89da58 "qemu-coroutine-lock.c", file@entry=0xb5660000 "\001", 
>     line=91, line@entry=3069931692, 
>     function=function@entry=0x7f89ab78 "qemu_co_queue_restart_all")
>     at assert.c:92
> #4  0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb5660000 "\001", 
>     line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all")
>     at assert.c:101
> #5  0x7f59a6b4 in ?? ()
> 
> I was using the same setup as in Bug 893208 (i.e git checkout from
> 2015-09-15)
> 
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
> 

This backtrace is next to useless I believe, but it's not your fault. I
think "scripts/qemu-gdb.py" might be helpful (it has a little bit of
documentation too). See also commit 9eddd6a4.

Thanks
Laszlo