From: Keith Owens <kaos@ocs.com.au>
To: caf@guarana.org
Cc: Kevin Easton <kevin@sylandro.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze
Date: Mon, 16 Dec 2002 15:47:32 +1100 [thread overview]
Message-ID: <8477.1040014052@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 16 Dec 2002 14:52:26 +1100." <20021216035226.GA30613@guarana.org>
On Mon, 16 Dec 2002 14:52:26 +1100,
caf@guarana.org wrote:
>Running with nmi_watchdog=2 has made the problem a bit harder to
>reproduce[1], but when it does hang it doesn't produce a trace (I left it
>for several minutes just in case..). Checking /proc/interrupts after
>boot shows around 16 NMIs, which I presume means that it's being used? -
>although it didn't seem to be going up at anything like once every 5
>seconds.
nmi_watchdog=2 should pop once per second, nmi_watchdog=1 pops HZ
(usually 100) times per second. Anything less than once a second is
not working. One possibility is CONFIG_X86_UP_APIC, it should be y for
UP to use nmi_watchdog.
>Is it possible that I'm not seeing the trace because I'm using a VGA
>virtual console rather than a real serial console?
Depends on your boot parameters for console and the levels of console
printk. Console output to X is unlikely to work, output to VGA
(including virtual consoles) should work. Except that some
distributions change printk levels and even redirect output to a
different virtual console.
cat /proc/cmdline should have no console setting or 'console=tty0'.
Change boot options and reboot if necessary.
cat /proc/sys/kernel/printk should report 6 4 1 7, if not then
echo "6 4 1 7" > /proc/sys/kernel/printk
next prev parent reply other threads:[~2002-12-16 4:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 0:51 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze Kevin Easton
2002-12-15 11:42 ` Keith Owens
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 [this message]
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=8477.1040014052@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=caf@guarana.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.