Get the backtrace of the loopback thread (using magic sysrq) and use
ksymoops to decode it using the System.map of your running kernel...
Thanks
On Mon, 17 Dec 2001, David Gomez wrote:
>
> Hi,
>
> Even with the Andrea/Monchil patch applied against 2.4.17-rc1, i'm still
> hitting the loopback deadlock. Doing a 'cp -a' to a loop device leaves cp
> and the loop kernel thread in D state.
>
> I don't know if it's useful, but i did a strace of cp, and the process is
> deadlocked in a mkdir call. Sometimes, a 'sync' finish the deadlock, other
> times sync also hangs:
>
> [...]
> 589 tty1 S 0:00 bash
> 594 ? DW< 0:00 [loop0]
> 620 tty1 D 0:00 sync
>
> And a reboot is the only way to kill the tasks.
>
>
> Thanks
>
> David Gómez
>
> "The question of whether computers can think is just like the question of
> whether submarines can swim." -- Edsger W. Dijkstra
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:14 EST