From: "Jan Beulich" <jbeulich@novell.com>
To: "Badari Pulavarty" <pbadari@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
<petkov@math.uni-muenster.de>, <akpm@osdl.org>,
"Andi Kleen" <ak@suse.de>, "lkml" <linux-kernel@vger.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Thu, 31 Aug 2006 09:35:03 +0200 [thread overview]
Message-ID: <44F6AD47.76E4.0078.0@novell.com> (raw)
In-Reply-To: <1156974410.16136.1.camel@dyn9047017100.beaverton.ibm.com>
Andi submitted a fix for this to Linus, but that's post-rc5. Jan
>>> Badari Pulavarty <pbadari@gmail.com> 30.08.06 23:46 >>>
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
next prev parent reply other threads:[~2006-08-31 7:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 1:31 boot failure, "DWARF2 unwinder stuck at 0xc0100199" J. Bruce Fields
2006-08-20 6:35 ` Andrew Morton
2006-08-20 8:26 ` Andi Kleen
2006-08-21 15:54 ` J. Bruce Fields
2006-08-21 16:03 ` Andi Kleen
2006-08-21 16:45 ` J. Bruce Fields
2006-08-28 9:50 ` Andi Kleen
2006-08-21 6:48 ` Jan Beulich
2006-08-21 16:47 ` Randy.Dunlap
2006-08-22 4:20 ` Andrew Morton
2006-08-22 8:01 ` Andi Kleen
2006-08-22 8:18 ` Jan Beulich
2006-08-22 17:42 ` J. Bruce Fields
2006-08-24 22:40 ` J. Bruce Fields
2006-08-24 23:16 ` Andi Kleen
2006-08-22 8:01 ` Jan Beulich
2006-08-22 8:22 ` Andi Kleen
2006-08-22 8:31 ` Jan Beulich
2006-08-22 8:34 ` Andi Kleen
2006-08-22 12:40 ` Jan Beulich
2006-08-28 22:32 ` Badari Pulavarty
2006-08-28 22:54 ` Andi Kleen
2006-08-28 23:50 ` Badari Pulavarty
2006-08-22 17:52 ` J. Bruce Fields
2006-08-25 10:16 ` [patch] lockdep: annotate idescsi_pc_intr() Ingo Molnar
2006-08-29 8:53 ` Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" Borislav Petkov
2006-08-29 9:57 ` Jan Beulich
2006-08-29 11:01 ` Borislav Petkov
2006-08-29 11:08 ` Jan Beulich
2006-08-29 11:16 ` Andi Kleen
2006-08-29 13:00 ` Borislav Petkov
2006-08-29 14:36 ` Andi Kleen
2006-08-29 14:59 ` Borislav Petkov
2006-08-30 21:46 ` Badari Pulavarty
2006-08-31 7:35 ` Jan Beulich [this message]
2006-08-31 7:41 ` Andi Kleen
2006-08-31 7:45 ` Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" II Andi Kleen
2006-08-31 7:48 ` Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" Jan Beulich
2006-08-31 15:02 ` Badari Pulavarty
2006-08-31 15:16 ` Andi Kleen
2006-08-31 16:29 ` Badari Pulavarty
2006-08-31 18:11 ` Badari Pulavarty
2006-08-31 18:10 ` Andi Kleen
2006-08-31 18:33 ` Badari Pulavarty
2006-08-31 18:32 ` Andi Kleen
2006-09-06 6:31 ` Keith Owens
2006-09-06 7:43 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-09-01 10:12 Chuck Ebbert
2006-09-01 10:21 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F6AD47.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=petkov@math.uni-muenster.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.