From: Keith Owens <kaos@ocs.com.au>
To: Pete Toscano <pete.lkml@toscano.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mysterious lockups with 2.4.X (Help w/KDB)
Date: Mon, 26 Feb 2001 10:33:04 +1100 [thread overview]
Message-ID: <10610.983143984@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 25 Feb 2001 13:39:16 CDT." <20010225133916.A1329@bubba.toscano.org>
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.
prev parent reply other threads:[~2001-02-25 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 18:39 Mysterious lockups with 2.4.X (Help w/KDB) Pete Toscano
2001-02-25 23:33 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10610.983143984@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pete.lkml@toscano.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox