From: Keith Owens <kaos@ocs.com.au>
To: Kevin Easton <kevin@sylandro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze
Date: Sun, 15 Dec 2002 22:42:40 +1100 [thread overview]
Message-ID: <1047.1039952560@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 13 Dec 2002 11:51:27 +1100." <20021213115127.A12153@beernut.flames.org.au>
On Fri, 13 Dec 2002 11:51:27 +1100,
Kevin Easton <kevin@sylandro.com> wrote:
>I'm not sure exactly where this problem fits in, but I'm getting a
>completely repeatable freeze (100% lockup, no response to keyboard)
>triggered by writing to /dev/st0 (dd if=/dev/urandom of=/dev/st0 bs=512
>count=163840 will reproduce it).
>So... does anyone have any ideas how I should start trying to track this
>down?
Boot with nmi_watchdog=1 (smp) or nmi_watchdog=2 (smp or up), cat
/proc/interrupts to verify that NMI is being used. If the problem is a
disabled spinloop then the watchdog will trip after 5 seconds and give
you a trace which can be run through ksymoops. If that trace does not
give enough data to debug the problem, apply the kdb patch[*], read
Documentation/kdb and start digging, bt first and debug from there.
[*] ftp://oss.sgi.com/projects/kdb/download/v2.5/
kdb-v2.5-2.4.19-common-1.bz2 + kdb-v2.5-2.4.19-i386-1.bz2 or
kdb-v2.5-2.4.20-common-1.bz2 + kdb-v2.5-2.4.20-i386-1.bz2
next prev parent reply other threads:[~2002-12-15 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 0:51 Kevin Easton
2002-12-15 11:42 ` Keith Owens [this message]
2002-12-15 12:49 ` caf
2002-12-15 20:01 ` Justin T. Gibbs
2002-12-15 21:52 ` kevin
2002-12-16 5:04 ` Kevin Easton
2002-12-16 3:52 ` caf
2002-12-16 4:47 ` Keith Owens
2002-12-16 5:21 ` Kevin Easton
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=1047.1039952560@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kevin@sylandro.com \
--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
Powered by JetHome