Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932287AbWH2LIX@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932287AbWH2LIX (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 29 Aug 2006 07:08:23 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932282AbWH2LIW
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 29 Aug 2006 07:08:22 -0400
Received: from public.id2-vpn.continvity.gns.novell.com ([195.33.99.129]:37573
	"EHLO emea1-mh.id2.novell.com") by vger.kernel.org with ESMTP
	id S932287AbWH2LIW (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 29 Aug 2006 07:08:22 -0400
Message-Id: <44F43C67.76E4.0078.0@novell.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.1 
Date: Tue, 29 Aug 2006 12:08:55 +0100
From: "Jan Beulich" <jbeulich@novell.com>
To: <petkov@math.uni-muenster.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, <akpm@osdl.org>,
       "Andi Kleen" <ak@suse.de>, <linux-kernel@vger.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
References: <20060820013121.GA18401@fieldses.org>
 <44E97353.76E4.0078.0@novell.com> <20060829085338.GA8225@gollum.tnic>
 <44F42BB1.76E4.0078.0@novell.com> <20060829110109.GA10944@gollum.tnic>
In-Reply-To: <20060829110109.GA10944@gollum.tnic>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1518
Lines: 33

>>> Borislav Petkov <bbpetkov@yahoo.de> 29.08.06 13:01 >>>
>On Tue, Aug 29, 2006 at 11:57:37AM +0200, Jan Beulich wrote:
>> >>> Borislav Petkov <bbpetkov@yahoo.de> 29.08.06 10:53 >>>
>> >Hi,
>> >    I just read that unwinder thread and I think I have yet another case of
>> >    unwinder backtrace that comes up together with the recursive deadlock
>> >    protection backtrace and this happens with 18-rc5 so I thought I should
>> >    report it before .18 is released:
>> >...
>> >Aug 29 10:21:22 zmei kernel: [  383.485261]  [<c0105393>] do_IRQ+0xc3/0xd0
>> >Aug 29 10:21:22 zmei kernel: [  383.489393]  [<c0103521>] common_interrupt+0x25/0x2c
>> >Aug 29 10:21:22 zmei kernel: [  383.494387] DWARF2 unwinder stuck at common_interrupt+0x25/0x2c
>> >Aug 29 10:21:22 zmei kernel: [  383.500304] Leftover inexact backtrace:
>> ></snip>
>> 
>> Unfortunately this leaves unclear whether there was anything reported in
>> the leftover portion.
>> And in all cases, a sufficiently long raw stack trace is needed to analyse this.
>> Ideally a matching System.map would also be attached.
>> 
>> Jan
>
>Actually, that's all there was in dmesg. System.map is at
>http://tim.dnsalias.org/System.map-2.6.18-rc5.

Without a hex dump of stack contents there's very little I can do.

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