This is definitely a serious bug. All interrupts of appropriate type
should be blocked during execution of exception handler.
It's definitely _not_ a correct fix to make kernel stack bigger
in hope to get "big enough".

Jaromir

Rafal Boni wrote:
> Folks:
> 	I've finally had a few minutes of quiet to chase down a problem I've
> 	been staring at on-and-off for a while: with a lot of output going 
> 	to the serial console & the console running at high speeds (38.4kbps
> 	in this case), my sgi kernels would generally fall over in several
> 	rather brutal ways (usually cache error panics or something else
> 	really non-intuitive).
> 
> 	I finally tracked down the problem to a kernel stack overflow due to
> 	too deep interrupt nesting... Here's a backtrace (the panic is a
> 	check I added to make tracking this down a bit easier):
> 
> 
> panic: cpu_intr: max_intr_depth too high: 16
> Stopped at      0x8815ee64:     jr      ra
>                 bdslot: nop
-- 
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/Ports/i386/ps2.html
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-