linux-kernel - Re: Was: 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]

Message-Id: <200608291636.56673.ak@suse.de>
Date:	Tue, 29 Aug 2006 16:36:56 +0200
From:	Andi Kleen <ak@...e.de>
To:	petkov@...h.uni-muenster.de
Cc:	Jan Beulich <jbeulich@...ell.com>,
	"J. Bruce Fields" <bfields@...ldses.org>, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

On Tuesday 29 August 2006 15:00, Borislav Petkov wrote:
> On Tue, Aug 29, 2006 at 01:16:22PM +0200, Andi Kleen wrote:
> > 
> > > 
> > > Without a hex dump of stack contents there's very little I can do.
> > 
> > Borislav, if you can reproduce the crash please boot with kstack=2048 and send output
> > of that.
> Yeah, 
>     that's a no-go, same output:

Can you please try it with this debug patch?

-Andi

Index: linux/arch/x86_64/kernel/traps.c
===================================================================
--- linux.orig/arch/x86_64/kernel/traps.c
+++ linux/arch/x86_64/kernel/traps.c
@@ -106,7 +106,7 @@ static inline void preempt_conditional_c
 	preempt_enable_no_resched();
 }
 
-static int kstack_depth_to_print = 12;
+static int kstack_depth_to_print = 2048;
 #ifdef CONFIG_STACK_UNWIND
 static int call_trace = 1;
 #else
@@ -418,7 +418,7 @@ void show_stack(struct task_struct *tsk,
 void dump_stack(void)
 {
 	unsigned long dummy;
-	show_trace(NULL, NULL, &dummy);
+	_show_stack(NULL, NULL, &dummy);
 }
 
 EXPORT_SYMBOL(dump_stack);
-
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/