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]

Date:	Thu, 31 Aug 2006 17:16:08 +0200
From:	Andi Kleen <ak@...e.de>
To:	Badari Pulavarty <pbadari@...il.com>
Cc:	Jan Beulich <jbeulich@...ell.com>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	petkov@...h.uni-muenster.de, akpm@...l.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

On Thursday 31 August 2006 17:02, Badari Pulavarty wrote:

> I will verify them when I get a chance to move to latest kernel.

Sorry I just meant the problem has been analyzed, but not fixed
yet (it is a bit tricky). Most of the fixes won't make 2.6.18
anyways because it's too late for that.

> Unfortunately, so called testcases are the *real* problems I am
> trying to track down in 2.6.18-rc4 and I have a setup/config/testcase
> which can reproduce them consistently. I don't want to change
> any kernel/config till I debug these issues. Once I figure out whats
> happening - I will move to latest and verify one more time.

Not needed right now.

> 
> Code: 0f 0b 68 d3 e0 50 80 c2 e7 0a 48 83 7b 38 00 75 0a 0f 0b 68
> RIP  [<ffffffff80282d39>] submit_bh+0x29/0x130
>  RSP <ffff8101bde8dd08>
>  <1>Unable to handle kernel paging request at 0000000146f4eac0 RIP:
>  [<ffffffff802277b8>] task_rq_lock+0x38/0x90
> PGD 1ddc2e067 PUD 0
> Oops: 0000 [2] SMP

Don't know why sorry, but it seems to be indeed before the unwinder. 
Maybe some state got messed up completely.

-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/