From: Andi Kleen <ak@suse.de>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Jan Beulich <jbeulich@novell.com>, Andrew Morton <akpm@osdl.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
lkml <linux-kernel@vger.kernel.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Tue, 29 Aug 2006 00:54:47 +0200 [thread overview]
Message-ID: <200608290054.47781.ak@suse.de> (raw)
In-Reply-To: <1156804352.447.5.camel@dyn9047017100.beaverton.ibm.com>
Thanks for the test cases. If you have more keep them comming.
> Call Trace:
> [<ffffffff80284179>] ll_rw_block+0x79/0xd0
> [<ffffffff8030e868>] journal_commit_transaction+0x478/0x1170
> [<ffffffff80312c8e>] kjournald+0xde/0x290
> [<ffffffff8024562c>] kthread+0xdc/0x110
> [<ffffffff8020abe2>] child_rip+0x8/0x12
> DWARF2 unwinder stuck at child_rip+0x8/0x12
> Leftover inexact backtrace:
> [<ffffffff80245550>] kthread+0x0/0x110
> [<ffffffff8020abda>] child_rip+0x0/0x12
I submitted Jan's patch to fix that one for .18, but Linus hasn't merged it
yet.
> [<ffffffff8027fbbc>] kfree+0x26/0x1f2
> [<ffffffff80304110>] do_get_write_access+0x52e/0x54f
> [<ffffffff803051a3>] journal_get_undo_access+0x2e/0x118
> [<ffffffff802f0a0c>] ext3_try_to_allocate_with_rsv+0x4b/0x504
> [<ffffffff802f117e>] ext3_new_blocks+0x2b9/0x74e
> [<ffffffff802f46d3>] ext3_get_blocks_handle+0x467/0xac4
> [<ffffffff802f5095>] ext3_get_block+0xc4/0xec
> [<ffffffff8028795c>] __block_prepare_write+0x1bf/0x41e
> [<ffffffff80287bdd>] block_prepare_write+0x22/0x30
> [<ffffffff802f660f>] ext3_prepare_write+0xb5/0x185
> [<ffffffff8025fbc3>] generic_file_buffered_write+0x2c7/0x6b7
> [<ffffffff80260298>] __generic_file_aio_write_nolock+0x2e5/0x331
> [<ffffffff8026034d>] generic_file_aio_write+0x69/0xc4
> [<ffffffff802f21a6>] ext3_file_write+0x1e/0x9b
> [<ffffffff80284804>] do_sync_write+0xf0/0x12e
> [<ffffffff80285197>] vfs_write+0xcf/0x175
> [<ffffffff8028577f>] sys_write+0x47/0x70
> [<ffffffff8020988e>] system_call+0x7e/0x83
> DWARF2 unwinder stuck at system_call+0x7e/0x83
This one will be fixed in .19 only
> Leftover inexact backtrace:
>
>
> Code: 0f 0b 68 ae 3c 4a 80 c2 8a 0a 58 5b c9 c3 55 48 89 e5 41 57
> RIP [<ffffffff8027de3d>] kfree_debugcheck+0x9a/0xa8
> RSP <ffff81010d9ad5b8>
> <3>BUG: sleeping function called from invalid context at
> kernel/rwsem.c:20
> in_atomic():0, irqs_disabled():1
>
> Call Trace:
> [<ffffffff8020ad7f>] show_trace+0xae/0x30e
> [<ffffffff8020aff4>] dump_stack+0x15/0x17
> [<ffffffff802288a5>] __might_sleep+0xb2/0xb4
> [<ffffffff8024750e>] down_read+0x1d/0x2f
> [<ffffffff8023e674>] blocking_notifier_call_chain+0x1b/0x41
> [<ffffffff80232511>] profile_task_exit+0x15/0x17
> [<ffffffff80233f95>] do_exit+0x25/0x91e
> [<ffffffff8020b222>] kernel_math_error+0x0/0x96
> [<ffff81010b6a30c0>]
Hmm, not sure about that one. In theory it should have been fixed
in rc4 already. Was this from an earlier kernel?
> DWARF2 unwinder stuck at 0xffff81010b6a30c0
> Leftover inexact backtrace:
> [<ffffffff80471079>] do_trap+0xe0/0xef
> [<ffffffff8020b82d>] do_invalid_op+0xa7/0xb3
> [<ffffffff8027de3d>] kfree_debugcheck+0x9a/0xa8
-Andi
next prev parent reply other threads:[~2006-08-28 23:01 UTC|newest]
Thread overview: 47+ 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 [this message]
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
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
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=200608290054.47781.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=rdunlap@xenotime.net \
/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.