From: Ross Dickson <ross@datscreative.com.au>
To: linux-kernel@vger.kernel.org
Cc: ross@datscreative.com.au, recbo@nishanet.com,
B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Mon, 8 Dec 2003 13:21:06 +1000 [thread overview]
Message-ID: <200312081321.06692.ross@datscreative.com.au> (raw)
On Monday 08 of December 2003 04:08, Bob wrote:
> >>Sounds great.. maybe you have come across something. Yes, the CPU
> >>Disconnect function arrived in your BIOS in revision of 2003/03/27
> >>"6.Adds"CPU Disconnect Function" to adjust C1 disconnects. The Chipset
> >>does not support C2 disconnect; thus, disable C2 function."
> >>
> >>For me though.. Im on an ASUS A7N8X Deluxe v2 BIOS 1007. From what I can
> >>see the CPU Disconnect isnt even in the Uber BIOS 1007 for this ASUS
> >>that has been discussed.
> >>
> >>Craig
> >
> >I don't have that in MSI K7N2 MCP2-T near the
> >agp and fsb spread spectrum items or anywhere
>> else.
>Use athcool:
> http://members.jcom.home.ne.jp/jacobi/linux/softwares.html#athcool
> or apply kernel patch (2.4 and 2.6 versions were posted already).
>--bart
Please take a look at
Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
in mailing list.
I approached it from another angle regarding delaying the apic ack in local timer irq
and achieved stability. It would be good to have others try it. Ian Kumlien is also
reporting success so far.
next reply other threads:[~2003-12-08 3:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 3:21 Ross Dickson [this message]
2003-12-08 11:36 ` Catching NForce2 lockup with NMI watchdog - found? Craig Bradney
2003-12-08 13:34 ` Ross Dickson
2003-12-08 17:40 ` Bob
2003-12-09 16:44 ` merged in bk5 " Bob
2003-12-09 16:43 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 22:57 b
2003-12-10 4:48 ` 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-06 0:55 Ian Kumlien
2003-12-06 1:52 ` Craig Bradney
2003-12-06 4:00 ` Mike Fedyk
2003-12-06 8:23 ` Josh McKinney
2003-12-08 3:12 ` Bob
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=200312081321.06692.ross@datscreative.com.au \
--to=ross@datscreative.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=recbo@nishanet.com \
/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