Re: Mysterious lockups with 2.4.X (Help w/KDB)

Keith Owens (kaos@ocs.com.au)
Mon, 26 Feb 2001 10:33:04 +1100

On Sun, 25 Feb 2001 13:39:16 -0500,
Pete Toscano <pete.lkml@toscano.org> wrote:
>Unable to handle kernel NULL pointer dereference at virtual address 0000017c
> printing eip:
>and then the KDB prompt appears. Back when I had my emu10k problems,
>Keith Owen told me to (in a nutshell), go through the running processes
>and "btp" their PID and look for "text.lock".

Those instructions were for a lockup. This problem is not a lockup, it
is a bad pointer. In this case you only care about the current
process. Backtrace (bt) will show what the process was doing. 'id
%eip' will disassemble the failing code.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/