From: Joerg Sommrey <jo175@sommrey.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: nmi watchdog failure on dual Athlon box
Date: Wed, 29 Sep 2004 22:27:50 +0200 [thread overview]
Message-ID: <20040929202750.GA5534@sommrey.de> (raw)
In-Reply-To: <Pine.LNX.4.58L.0409282159480.24587@blysk.ds.pg.gda.pl>
On Tue, Sep 28, 2004 at 10:08:21PM +0100, Maciej W. Rozycki wrote:
> On Tue, 28 Sep 2004, Joerg Sommrey wrote:
>
> > |--- lockupcli.c
> > |
> > |main ()
> > |{
> > | iopl(3);
> > | for (;;) asm("cli");
> > |}
> >
> > Does this mean there is a good reason for further investigations on why
> > the IO-APIC NMI watchdog doesn't work? Until now I thought it would
> > be ok as long as the local APIC NMI watchdog is set up.
>
> Since this program does busy looping, the local APIC NMI watchdog should
> trigger indeed. It's "cli; hlt" that causes a problem with this watchdog.
> Something wrong is happening in your system, indeed.
As I stated earlier, there *seemed* to be a working IO-APIC NMI watchdog
with 2.6.3-mm4. I never checked it's functionallity. Now I rebuilt that
kernel and gave it a try. Though it claims to have a running IO-APIC NMI
watchdog, the lockupcli test failed. Zwane was right when he suspected the
nmi_watchdog=1 test working erratically in that case. Sad but true: no NMI
watchdog on tyan S2466. I wonder if it's just impossible on such a board
or if it needs some "special treatment"
-jo
--
-rw-r--r-- 1 jo users 63 2004-09-29 22:10 /home/jo/.signature
next prev parent reply other threads:[~2004-09-29 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 16:33 nmi watchdog failure on dual Athlon box Joerg Sommrey
2004-09-28 17:08 ` Maciej W. Rozycki
2004-09-28 18:31 ` Joerg Sommrey
2004-09-28 21:08 ` Maciej W. Rozycki
2004-09-29 20:27 ` Joerg Sommrey [this message]
2004-09-28 20:20 ` Chris Wedgwood
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=20040929202750.GA5534@sommrey.de \
--to=jo175@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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