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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: "Eric Rannaud" <[email protected]>
- Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- From: Peter Zijlstra <[email protected]>
- BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Prev by Date: Re: [2.6.18-git] Lost all PCI devices
- Next by Date: Re: GPLv3 Position Statement
- Previous by thread: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Next by thread: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
- Index(es):
 |