I should mention also, that kdb ALWAYS shows the same CPU: 1. It never ends
up on 0, or 2-7. I thought this was curious... is this some sort of default
behavior? Or does this possibly help indicate the problem?
TIA,
-Matt
Keith Owens wrote:
>
> On Wed, 15 May 2002 18:03:29 -0700,
> Patricia Gaughen <gone@xxxxxxxxxx> wrote:
> >2.5.9 on an 8 proc numaq box. I saw the recent patch from Ethan Solomita and
> >I'll give it a try tonight or tomorrow. But we've ran into a couple of
> >issues:
> >
> > - when the system hangs we enter kdb but using bt, bta and btp do not
> > produce
> >stacks for any of the processes. We're able to get the stacks manually, but
> >this is not much fun :-)
>
> Which version of gcc? Newer versions of gcc produce stack frame code
> that kdb cannot backtrace without CONFIG_FRAME_POINTER=y.
>
> > - Also we're not able to switch cpus.
>
> If the cpu command only displays one cpu then the others have been shut
> down. By the time that kdb is called from the panic() routine, the
> panic code has already disabled all the other cpus.
|