From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Mon, 21 Aug 2006 12:45:50 -0400 [thread overview]
Message-ID: <20060821164550.GB3678@fieldses.org> (raw)
In-Reply-To: <200608211803.28867.ak@suse.de>
On Mon, Aug 21, 2006 at 06:03:28PM +0200, Andi Kleen wrote:
> On Monday 21 August 2006 17:54, J. Bruce Fields wrote:
> > On Sun, Aug 20, 2006 at 10:26:54AM +0200, Andi Kleen wrote:
> > >
> > > > DWARF2 unwinder stuck at 0xc0100199
> > > > Leftover inexact backtrace:
> > > > =======================
> > > > BUG: unable to handle kernel paging request at virtual address 0000b034
> > >
> > > This is already fixed in mainline.
> >
> > I'm seeing the same behavior on Linus's latest as of this morning
> > (2.6.18-rc4-gef7d1b24). Is there something else I should be testing?
>
> The stuck is expected, but the unable to handle paging request should be
> fixed. If not then it's a different problem than what I'm thinking,
> but it looks very similar.
OK, so any suggestions for what I should try?
My most recent panic on boot ended with:
DWARF2 unwinder tack at 0xc0100199
Leftover inexact backtrace:
=======================
BUG: unable to handle kernel paging requets at virtual address 0000b034
printing eip:
c0103712
*pde = 00000000
Recursive die() failure, output suppressed
<0>Kernel panic - not syncing: Fatal exception in interrupt
Taking a look at an "objdump -d vmlinux", that c0103712 is in
show_trace_log_lvl():
...
c01036f9: e8 a2 33 01 00 call c0116aa0 <printk>
c01036fe: 53 push %ebx
c01036ff: 68 4c 20 5a c0 push $0xc05a204c
c0103704: e8 67 41 03 00 call c0137870 <__print_symbol>
c0103709: 8b 06 mov (%esi),%eax
c010370b: 83 c4 10 add $0x10,%esp
c010370e: 39 c6 cmp %eax,%esi
c0103710: 75 ce jne c01036e0 <show_trace_log_lvl+0x60>
-->c0103712: 8b 4f 34 mov 0x34(%edi),%ecx
c0103715: 85 c9 test %ecx,%ecx
c0103717: 74 14 je c010372d <show_trace_log_lvl+0xad>
c0103719: 89 cb mov %ecx,%ebx
c010371b: 8b 4d 08 mov 0x8(%ebp),%ecx
c010371e: 51 push %ecx
c010371f: 68 06 aa 59 c0 push $0xc059aa06
c0103724: e8 77 33 01 00 call c0116aa0 <printk>
...
It looks like that's the deference of context on line 221:
stack = (unsigned long*)context->previous_esp;
So "context" was 0000b000?? OK, I don't know this code at all, so I'm
probably not going to figure out anything useful here.
--b.
next prev parent reply other threads:[~2006-08-21 16:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 1:31 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 [this message]
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
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=20060821164550.GB3678@fieldses.org \
--to=bfields@fieldses.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®