From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sat, 6 Dec 2003 03:23:12 -0500 [thread overview]
Message-ID: <20031206082312.GA1730@forming> (raw)
In-Reply-To: <1070675560.4117.9.camel@athlonxp.bradney.info>
On approximately Sat, Dec 06, 2003 at 02:52:40AM +0100, Craig Bradney wrote:
> Ok.. I decided I would try the patch out.. here are the results:
>
[snip]
I tried it out too since doing some greps after 3 days uptime crashed
it again. Guess I am not so lucky. So far so good with the new
patch, timer is using apic and no crashes yet, after 30 minutes of
grep's and hdparms. Tried booting with nmi_watchdog=1 and got this:
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.
activating NMI Watchdog ... done.
testing NMI watchdog ... CPU#0: NMI appears to be stuck!
Going to retry with nmi_watchdog=2 and see if that works.
>
> Im not getting any NMI counts.. should I use nmi-watchdog=1?
>
>
[snip]
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
| They that can give up essential liberty
Linux, the choice -o) | to obtain a little temporary safety deserve
of the GNU generation /\ | neither liberty or safety.
_\_v | -Benjamin Franklin
next prev parent reply other threads:[~2003-12-06 8:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 0:55 Catching NForce2 lockup with NMI watchdog - found? Ian Kumlien
2003-12-06 1:52 ` Craig Bradney
2003-12-06 4:00 ` Mike Fedyk
2003-12-06 8:23 ` Josh McKinney [this message]
2003-12-08 3:12 ` Bob
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 22:57 merged in bk5 " b
2003-12-10 4:48 ` Bob
2003-12-08 3:21 Ross Dickson
2003-12-08 11:36 ` Craig Bradney
2003-12-08 13:34 ` Ross Dickson
2003-12-08 17:40 ` Bob
2003-12-06 19:33 Ian Kumlien
2003-12-07 0:20 ` Craig Bradney
2003-12-07 0:29 ` Ian Kumlien
2003-12-07 10:32 ` Craig Bradney
2003-12-07 14:54 ` Ian Kumlien
2003-12-06 2:08 Ian Kumlien
2003-12-06 13:36 ` Craig Bradney
2003-12-06 13:47 ` Bartlomiej Zolnierkiewicz
2003-12-06 14:42 ` Ian Kumlien
2003-12-06 15:33 ` Craig Bradney
2003-12-06 15:58 ` Ian Kumlien
2003-12-06 1:58 Ian Kumlien
2003-12-05 20:56 Catching NForce2 lockup with NMI watchdog Allen Martin
2003-12-05 23:49 ` Catching NForce2 lockup with NMI watchdog - found? Prakash K. Cheemplavam
2003-12-05 23:55 ` Prakash K. Cheemplavam
2003-12-06 0:15 ` Craig Bradney
2003-12-06 0:21 ` Prakash K. Cheemplavam
2003-12-06 0:37 ` Craig Bradney
2003-12-08 3:08 ` Bob
2003-12-08 3:06 ` Bartlomiej Zolnierkiewicz
2003-12-08 3:03 ` Bob
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=20031206082312.GA1730@forming \
--to=forming@charter.net \
--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).