[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0609301322530.3952@g5.osdl.org>
Date: Sat, 30 Sep 2006 13:23:53 -0700 (PDT)
From: Linus Torvalds <torvalds@...l.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
cc: Eric Rannaud <eric.rannaud@...il.com>,
linux-kernel@...r.kernel.org, mingo@...e.hu, akpm@...l.org,
nagar@...son.ibm.com, Ravikiran G Thirumalai <kiran@...lex86.org>
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
On Sat, 30 Sep 2006, Peter Zijlstra wrote:
>
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm1/broken-out/slab-fix-lockdep-warnings.patch
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm1/broken-out/slab-fix-lockdep-warnings-fix.patch
> http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm1/broken-out/slab-fix-lockdep-warnings-fix-2.patch
>
> Those should rid you off the trace seen under:
Well, the more serious problem seems to be that any warning that causes a
back-trace on x86-64 seems liable to just lock up due to the backtrace
code itself being buggy.
At least I _hope_ its x86-64 only.
Linus
-
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