Re: RC3 LOCKDEBUG panic on 6-way E3k.

[Martin Husemann <martin%duskware.de@localhost>]

On Sun, Mar 22, 2009 at 03:27:40PM +0100, Anders Lindgren wrote:
>   I got an RC3 DIAGNOSTICS+DEBUG+LOCKDEBUG kernel running with changes 
> suggested by Martin. Foor good measure, I eliminated RAIDframe from the 
> picture by booting a second install from a different disk and started a 
> build.sh -j8 release-build on it to kill it. Rather than deadlock hard 
> within 10 minutes, it now survived 37 minutes -- but then it panicked! But 
> now I have ddb!

It's running out of mmu contexts on one of the cpus - and something goes
wrong in the code supposed to recover from that (not realy a heavily tested
code path). I'll have to read the code again and try to see if can reproduce
it with aritificially limited number of contexts quicker on a local machine.

Martin