From: Keith Owens <kaos@ocs.com.au>
To: kees <kees@schoen.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hang with SMP 2.4.4 snd log
Date: Mon, 21 May 2001 19:39:23 +1000 [thread overview]
Message-ID: <9363.990437963@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 21 May 2001 10:26:20 +0200." <Pine.LNX.4.21.0105211022430.4818-200000@schoen3.schoen.nl>
On Mon, 21 May 2001 10:26:20 +0200 (CEST),
kees <kees@schoen.nl> wrote:
>I got a next hang with my SMP system, kdb log attached. Something strange
>with the backtrace for CPU 0. Here is the first cut from the kdb log..
I do not trust either of those backtraces. There is no way to get from
do_nmi to do_exit. The presence of "unknown" entries indicates that
the cpu 0 back trace is bad. Also all the ebp pointers are suspect,
they are way out of range for the task addresses. You could be looking
at a stack overrun or just random corruption of kernel data.
If you can reproduce the problem, set KDBDEBUG=0xff and bt. That will
debug kdb and produce a lot of output. Send it to me, although I
suspect it will just prove that you have stack corruption.
prev parent reply other threads:[~2001-05-21 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 8:26 Hang with SMP 2.4.4 snd log kees
2001-05-21 9:39 ` 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=9363.990437963@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=kees@schoen.nl \
--cc=linux-kernel@vger.kernel.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