From: Keith Owens <kaos@ocs.com.au>
To: "T. A." <tkhoadfdsaf@hotmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Consistant complete deadlock with kernel 2.4.16 on an Abit VP6 with dual 1 Gig CPUs and an ICP GDT RAID card
Date: Fri, 21 Dec 2001 01:10:26 +1100 [thread overview]
Message-ID: <24576.1008857426@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 19 Dec 2001 16:22:47 CDT." <OE272TUSzbAUfKRfcjc00005359@hotmail.com>
On Wed, 19 Dec 2001 16:22:47 -0500,
"T. A." <tkhoadfdsaf@hotmail.com> wrote:
> Anyone know how I could debug the cause of this problem? Machine
>deadlocks. Not even an Ooops so I'm short on ideas on how to track the
>problem down. Please help. 8-( My new SMP system sucks on Linux. 8-(
Compile for SMP and boot with nmi_watchdog=1. If the problem is
hardware that will not help. If the problem is a software loop in
kernel space (much more likely) then the nmi watchdog will trip after 5
seconds.
You might also find the kernel debugger to be useful,
ftp://oss.sgi.com/projects/kdb/download/ix86. See Documentation/kdb
for man pages. Using the pause key on a PC keyboard or control-A on a
serial console will drop into kdb, unless the kernel has stopped
processing interuupts, in which case the nmi watchdog should trip and
drop you into kdb.
For all low level debugging, I strongly recommend a serial console so
you can capture the output on another system, see
Documentation/serial-console.txt.
next prev parent reply other threads:[~2001-12-20 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 21:22 T. A.
2001-12-20 14:10 ` Keith Owens [this message]
2001-12-20 15:00 ` Alex
2001-12-21 1:25 ` T. A.
2001-12-23 23:29 ` Alex
2001-12-20 15:40 ` Dennis Schoen
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=24576.1008857426@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tkhoadfdsaf@hotmail.com \
/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
all inboxes | Powered by JetHome®