I have found the EIP of where it is stuck, it's stuck at testb according to
the ps output, is ps incorrect, as in the granularity of WCHAN is too vague
to say exactly where it is?
I can't debug this at the console until tomorrow night. I'm _really_ hoping
to get this fixed before then.
-d
On Tue, 21 Mar 2000, Manfred Spraul wrote:
> Date: Tue, 21 Mar 2000 10:10:17 +0100
> From: Manfred Spraul <manfreds@colorfullife.com>
> To: Blu3Viper <david@killerlabs.com>
> Subject: Re: (FOUND - Need patch) bad bad unknown brokeness
>
> > where is this program 'btp' found?
> It's a command that you can enter on the kdb console:
> * apply the kdb patch.
> http://oss.sgi.com/projects/kdb/
> * reboot
> * run apache/wget until a process is stuck.
> * IIRC press <PAUSE>, now you enter the kdb console
> and try btp.
>
> Or you could print the task pointer ("current") in your own patch.
> Then you dump the 8 kB task area.
>
> gdb --core /proc/kcore
> x/2048x <your current pointer>
>
> Then you need a clever script that adds "[<" and ">]" around the numbers,
> and you parse the numbers through ksymoops.
>
> Note that you might only find where the kernel is stuck, but often this
> won't show you why it is stuck :-(
> --
> Manfred
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:32 EST