public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	"Badari Pulavarty" <pbadari@gmail.com>,
	<petkov@math.uni-muenster.de>, <akpm@osdl.org>,
	"lkml" <linux-kernel@vger.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
Date: Thu, 31 Aug 2006 09:48:50 +0200	[thread overview]
Message-ID: <44F6B082.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200608310941.40076.ak@suse.de>

>>> Andi Kleen <ak@suse.de> 31.08.06 09:41 >>>
>On Thursday 31 August 2006 09:35, Jan Beulich wrote:
>> Andi submitted a fix for this to Linus, but that's post-rc5. Jan
>
>I assume you mean the fallback validation fix. Linus unfortunately
>didn't merge any of my new patches yet :/

Actually, the same patch, but other pieces of it ...

>But did you ever work out why the stack backtrace completely restarted? 
>I never got this. In theory the RSP gotten out of the unwind
>context and used for the fallback should have been already near the end
>and the old unwinder shouldn't have found much.

In the old (up to -rc5) code, we had

		if (unw_ret > 0 && !arch_unw_user_mode(&info)) {
			< all the fallback handling>
		}

with no else, thus just falling through (without even changing the
stack pointer, which was wrong when unw_ret > 0 but we reached
a user mode address (i.e. as in the example here, after unwinding
out of a syscall frame).

Jan

  parent reply	other threads:[~2006-08-31  7:48 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
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                 ` Jan Beulich [this message]
2006-08-31 15:02                 ` Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" 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=44F6B082.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox