Re: Loopback deadlock again

From: Momchil Velikov (velco@fadata.bg)
Date: Tue Dec 18 2001 - 10:31:19 EST


(sorry for posting twice, but you mail bounced)

>>>>> "David" == David Gómez <davidge@jazzfree.com> writes:

David> On Mon, 17 Dec 2001, Marcelo Tosatti wrote:
>>
>> Get the backtrace of the loopback thread (using magic sysrq) and use
>> ksymoops to decode it using the System.map of your running kernel...

David> Trace; c01304f8 <__wait_on_buffer+68/90>
David> Trace; c0131d69 <__block_prepare_write+239/260>
David> Trace; c012ac61 <__alloc_pages+41/180>
David> Trace; c0132271 <block_prepare_write+21/40>
David> Trace; c014e260 <ext2_get_block+0/410>
David> Trace; e08522df <[loop]lo_send+df/1e0>
David> Trace; e08522df <[loop]lo_send+df/1e0>

Can you recompile without -fomit-frame-pointer ? The back trace
doesn't look right.

Regards,
-velco

-
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:16 EST