On Fri, 27 Jun 2014 14:50:27 +0200
Paolo Bonzini <[email protected]> wrote:

> Il 27/06/2014 14:45, Luiz Capitulino ha scritto:
> > On Thu, 26 Jun 2014 23:24:09 +0200
> > Paolo Bonzini <[email protected]> wrote:
> >
> >> Il 26/06/2014 22:19, Luiz Capitulino ha scritto:
> >>> Here goes a gdb backtrace:
> >>>
> >>> #0  0x00007f298ce31759 in syscall () from /lib64/libc.so.6
> >>> #1  0x00007f29939b0b56 in futex_wait (ev=0x7f2994548f18, val=4294967295)
> >>>     at 
> >>> /home/lcapitulino/work/src/upstream/qmp-unstable/util/qemu-thread-posix.c:304
> >>> #2  0x00007f29939b0c68 in qemu_event_wait (ev=0x7f2994548f18)
> >>>     at 
> >>> /home/lcapitulino/work/src/upstream/qmp-unstable/util/qemu-thread-posix.c:400
> >>> #3  0x00007f299392a066 in qemu_clock_enable (type=QEMU_CLOCK_VIRTUAL, 
> >>> enabled=false)
> >>>     at /home/lcapitulino/work/src/upstream/qmp-unstable/qemu-timer.c:171
> 
> 
> /* Disabling the clock will wait for related timerlists to stop
>   * executing qemu_run_timers.  Thus, this functions should not
>   * be used from the callback of a timer that is based on @clock.
>   * Doing so would cause a deadlock.
>   */
> 
> It does indeed.  I'll post a fix during hard freeze.

Thanks Paolo!

Reply via email to