Am 19.05.2010 um 10:18 schrieb Peter Lieven:
> Kevin Wolf wrote:
>> Am 19.05.2010 09:29, schrieb Christoph Hellwig:
>>
>>> On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
>>>
I think it's stuck here in an endless loop:
while (laiocb->ret == -EINPROGRESS)
Kevin Wolf wrote:
Am 19.05.2010 09:29, schrieb Christoph Hellwig:
On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
I think it's stuck here in an endless loop:
while (laiocb->ret == -EINPROGRESS)
qemu_laio_completion_cb(laiocb->ctx);
Can you verify this by single
Am 19.05.2010 09:29, schrieb Christoph Hellwig:
> On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
>> I think it's stuck here in an endless loop:
>>
>> while (laiocb->ret == -EINPROGRESS)
>> qemu_laio_completion_cb(laiocb->ctx);
>>
>> Can you verify this by single-stepping on
On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
> I think it's stuck here in an endless loop:
>
> while (laiocb->ret == -EINPROGRESS)
> qemu_laio_completion_cb(laiocb->ctx);
>
> Can you verify this by single-stepping one or two loop iterations? ret
> and errno after the re
Am 18.05.2010 13:10, schrieb Peter Lieven:
> hi kevin,
>
> here is the backtrace of (hopefully) all threads:
>
> ^C
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 0x7f39b72656f0 (LWP 10695)]
> 0x7f39b6c3ea94 in __lll_lock_wait () from /lib/libpthread.so.0
>
> (gdb) threa
hi kevin,
here is the backtrace of (hopefully) all threads:
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7f39b72656f0 (LWP 10695)]
0x7f39b6c3ea94 in __lll_lock_wait () from /lib/libpthread.so.0
(gdb) thread apply all bt
Thread 2 (Thread 0x7f39b57b8950 (LWP 10698)):
Hi Peter,
Am 12.05.2010 16:01, schrieb Peter Lieven:
> Hi Kevin,
>
> here we go. I created a blocking multipath device (interrupted all
> paths). qemu-kvm hangs with 100% cpu.
> also monitor is not responding.
>
> If I restore at least one path, the vm is continueing.
>
> BR,
> Peter
This see
