From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Badari Pulavarty" <pbadari@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
petkov@math.uni-muenster.de, akpm@osdl.org,
"lkml" <linux-kernel@vger.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199" II
Date: Thu, 31 Aug 2006 09:45:58 +0200 [thread overview]
Message-ID: <200608310945.58728.ak@suse.de> (raw)
In-Reply-To: <200608310941.40076.ak@suse.de>
On Thursday 31 August 2006 09:41, Andi Kleen wrote:
> 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 :/
To follow myself up. I should have checked HEAD before writing this :/
Linus merged it all last night and I blamed him wrongly, sorry.
So that problem will be hopefully gone.
For completeness the unwind fixes that went in were:
Jan Beulich [PATCH] x86: Make backtracer fallback logic more bullet-proof
Andi Kleen [PATCH] i386: Add kernel thread stack frame termination
Andi Kleen [PATCH] x86_64: Add kernel thread stack frame termination
and this one fixed an additional bug in the old x86-64 unwinder:
Keith Owens [PATCH] x86_64: Save original IST values for checking
-Andi
next prev parent reply other threads:[~2006-08-31 7:46 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
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 ` Andi Kleen [this message]
2006-08-31 7:48 ` 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=200608310945.58728.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=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