public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Andrew Morton" <akpm@osdl.org>, "Andi Kleen" <ak@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	<linux-kernel@vger.kernel.org>,
	"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Tue, 22 Aug 2006 10:18:49 +0200	[thread overview]
Message-ID: <44EADA09.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200608221001.36124.ak@suse.de>

>> Has anyone even tried to reproduce Bruce's crash?
>
>I looked at it a bit, but it puzzles me. The chaining for the interrupt stacks
>on i386 -- which is what seems to be corrupted here -- shouldn't have changed at all 
>by the unwinder changes.

Not necessarily:

	if (UNW_SP(&info))
		stack = (void *)UNW_SP(&info);

is rather fragile - the minimum extra protection here should be to only use
UNW_SP() for the continuation stack pointer if it actually points into kernel
space (as is being done in one of the 2.6.19 patches), ...

>I suspect it would crash without unwinder too. Bruce, do you get the 
>same crash when you boot with "call_trace=old" ? 

... but of course I continue to agree that doing things like

	addr = *stack++;

in the legacy stack trace code cannot be good, given that this code
generally is expected to run when things are already bad in some way.

Jan

  reply	other threads:[~2006-08-22  8:18 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 [this message]
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=44EADA09.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox