linux-kernel - Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Aug 2006 01:16:08 +0200
From:	Andi Kleen <ak@...e.de>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	Andrew Morton <akpm@...l.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Jan Beulich <jbeulich@...ell.com>, linux-kernel@...r.kernel.org
Subject: Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

On Friday 25 August 2006 00:40, J. Bruce Fields wrote:
> On Tue, Aug 22, 2006 at 01:42:51PM -0400, J. Bruce Fields wrote:
> > On Tue, Aug 22, 2006 at 10:01:36AM +0200, Andi Kleen wrote:
> > > On Tuesday 22 August 2006 06:20, Andrew Morton wrote:
> > > > 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.
> > > 
> > > I suspect it would crash without unwinder too. Bruce, do you get the 
> > > same crash when you boot with "call_trace=old" ? 
> > 
> > After appending "call_trace=old" to the boot commandline, and it booted
> > succesfully.
> 
> Do you consider this closed, or do you need more information from me?

It's not closed, but i can probably reproduce it myself.
-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/