[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200610010024.53854.ak@suse.de>
Date: Sun, 1 Oct 2006 00:24:53 +0200
From: Andi Kleen <ak@...e.de>
To: "Eric Rannaud" <eric.rannaud@...il.com>
Cc: "Linus Torvalds" <torvalds@...l.org>,
"Ingo Molnar" <mingo@...e.hu>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...l.org>, nagar@...son.ibm.com,
"Chandra Seetharaman" <sekharan@...ibm.com>,
"Jan Beulich" <jbeulich@...ell.com>
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) II
On Sunday 01 October 2006 00:19, Eric Rannaud wrote:
> On 10/1/06, Andi Kleen <ak@...e.de> wrote:
> > I double checked this now. This case Eric ran into should be already
> > fixed by a patch from Jan that went in before 2.6.18 even.
> >
> > He just ran with an old kernel (2.6.18-rc3) that didn't have
> > that particular fix.
>
> Hmm, not sure I'm following you, but I did try with the released
> v2.6.18 (fourth stacktrace in my first email in this thread). The
> 2.6.13-rc3 (d94a041519f3ab1ac023bf917619cd8c4a7d3c01) version was
> tested only as the result of git-bisect, and is the first kernel that
> crashed in this way. But v2.6.18 crashed in a similar way as well.
> Are you saying v2.6.18 should contain a fix preventing it from crashing?
2.6.18 should have showed the backtrace from lockdep, but not the oops at
the end of the backtrace in show_trace()
-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/
Powered by blists - more mailing lists