From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Locked up 2.4.10-pre11 on Tyan 815t motherboard.
Date: Mon, 24 Sep 2001 11:14:21 -0400 [thread overview]
Message-ID: <200109241514.f8OFEL005589@deathstar.prodigy.com> (raw)
In-Reply-To: <3BA8DF59.B9F536B4@candelatech.com>
In article <3BA8DF59.B9F536B4@candelatech.com> greearb@candelatech.com wrote:
| Andrew Morton wrote:
|
| > nmi_watchdog will force an oops if the machine locks up
| > with interrupts disabled (as I suspect mine did). But
| > it requires an SMP kernel or IO-APIC-on-UP.
|
| I just built a 2.4.8 kernel with the APIC enabled. It locked
| hard and printed no OOPS. I had set the boot cmd line as:
| nmi_watchdog=1
This only works if you have a lock with no response. If keyboard input
is echoed or ping still works, that's not the tight lockup. May I
suggest the software watchdog feature as an alternative. It's much
better at finding cases where the system is only braindead rather than
locked up.
--
bill davidsen <davidsen@tmr.com>
"If I were a diplomat, in the best case I'd go hungry. In the worst
case, people would die."
-- Robert Lipe
next prev parent reply other threads:[~2001-09-24 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:51 Locked up 2.4.10-pre11 on Tyan 815t motherboard Ben Greear
2001-09-19 7:10 ` Ben Greear
[not found] ` <3BA8CCF1.CA2933B3@zip.com.au>
[not found] ` <3BA8D351.F57BE70D@candelatech.com>
[not found] ` <3BA8D619.9A607219@zip.com.au>
2001-09-19 18:09 ` Ben Greear
2001-09-24 15:14 ` bill davidsen [this message]
2001-09-24 18:18 ` Ben Greear
2001-09-19 18:38 ` Bruce Harada
2001-09-19 19:15 ` Alan Cox
2001-09-19 19:53 ` Ben Greear
2001-09-19 20:03 ` Jeff Garzik
2001-09-19 20:05 ` Alan Cox
2001-09-19 20:40 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard. [EEPRO-100 bugs] Ben Greear
2001-09-19 21:57 ` Alan Cox
2001-09-20 19:28 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard Martin Josefsson
2001-09-19 19:46 ` Ben Greear
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=200109241514.f8OFEL005589@deathstar.prodigy.com \
--to=davidsen@tmr.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;
as well as URLs for NNTP newsgroup(s).