Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

From: Badari Pulavarty
Date: Wed Aug 30 2006 - 17:40:47 EST


I ran into another (small) issue with the trace - it looks like
for some reason trace repeats twice. Do you know, why ?

Thanks,
Badari

Call Trace:
[<ffffffff8020b395>] show_trace+0xb5/0x370
[<ffffffff8020b665>] dump_stack+0x15/0x20
[<ffffffff8030d3b9>] journal_invalidatepage+0x309/0x3b0
[<ffffffff802fe898>] ext3_invalidatepage+0x38/0x40
[<ffffffff80282750>] do_invalidatepage+0x20/0x30
[<ffffffff80260820>] truncate_inode_pages_range+0x1e0/0x300
[<ffffffff80260950>] truncate_inode_pages+0x10/0x20
[<ffffffff802686ff>] vmtruncate+0x5f/0x100
[<ffffffff8029d7d0>] inode_setattr+0x30/0x140
[<ffffffff802ff81b>] ext3_setattr+0x1bb/0x230
[<ffffffff8029da3e>] notify_change+0x15e/0x320
[<ffffffff8027f973>] do_truncate+0x53/0x80
[<ffffffff802800f8>] sys_ftruncate+0xf8/0x130
[<ffffffff80209d5a>] system_call+0x7e/0x83
[<00002b40b67e1c47>]
[<ffffffff8030d3b9>] journal_invalidatepage+0x309/0x3b0
[<ffffffff802fe898>] ext3_invalidatepage+0x38/0x40
[<ffffffff80282750>] do_invalidatepage+0x20/0x30
[<ffffffff80260820>] truncate_inode_pages_range+0x1e0/0x300
[<ffffffff802fc203>] __ext3_get_inode_loc+0x163/0x350
[<ffffffff80260950>] truncate_inode_pages+0x10/0x20
[<ffffffff802686ff>] vmtruncate+0x5f/0x100
[<ffffffff8029d7d0>] inode_setattr+0x30/0x140
[<ffffffff802ff81b>] ext3_setattr+0x1bb/0x230
[<ffffffff8029da3e>] notify_change+0x15e/0x320
[<ffffffff8027f973>] do_truncate+0x53/0x80
[<ffffffff80281af1>] generic_file_llseek+0x91/0xb0
[<ffffffff802800f8>] sys_ftruncate+0xf8/0x130
[<ffffffff80209d5a>] system_call+0x7e/0x83




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/