Patricia Gaughen wrote:
>
> Matt Dobson and myself are trying to use kdb to debug a hang during boot on
> 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:
>
There have been a few -- there was a 3-line fix I sent out after that,
and then the i386 patch in a third email. Sorry if that's confusing.
> - 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 :-)
>
> - Also we're not able to switch cpus.
>
> Are these known issues? Should I expect Ethan's patch to help with this? and
> finally, where would you suggest I go from here (in terms of getting either of
> the issues above fixed).
>
Those are wierd. I know that, on sparc64 at least, I cannot use btp to
backtrace a process which was running on a CPU when kdb was entered. I
need to switch to that CPU first. But the symptoms you're describing
sound like things hung so badly that kdb isn't coping. If your problem
involves memory corruption, it is possible that it has damaged kdb's
ability to work.
-- Ethan
