From: really bensoo_at_soo_dot_com <lnx-kern@soo.com>
To: Ross Dickson <ross@datscreative.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Updated Lockup Patches, 2.6.0 Nforce2, apic timer ack delay, ioapic edge for NMI debug
Date: Wed, 24 Dec 2003 12:49:44 -0500 [thread overview]
Message-ID: <20031224124944.A1004@Sophia.soo.com> (raw)
In-Reply-To: <200312211917.05928.ross@datscreative.com.au>; from ross@datscreative.com.au on Sun, Dec 21, 2003 at 07:17:05PM +1000
i have an MSI K7N2, the original NFORCE2
chipset that doesn't do over 200MHz FSB,
running an overclocked Barton 2500 at
195MHz FSB, on 1Gig RAM.
These patches have worked for me. At
apic_tack=2 been up for close to two days
running the kind of load that before would
lock up the box in less than an hour.
So nice to have a reliable box again.
Season's Greetings; many thanks,
b
On Sun, Dec 21, 2003 at 07:17:05PM +1000, Ross Dickson wrote:
> Do my patches Fix all of it?
> No they are just workarounds. How well they work around may depend upon your
> system configuration, and how well the delay times chosen suit it.
>
> Any evil side effects?
> Maybe, but I don't know of any yet. Any slowing from the delay is so far
> not noticeable.
>
> Why 2 patches?
> The apic timer ack delay patch is for the hard lockups.
> The io-apic edge patch is for lost interrupts and also gives nmi_watchdog=1
> functionality.
>
> Should I install any or both?
> Depends, you get to decide until the manufacturers fix it.
>
next prev parent reply other threads:[~2003-12-24 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 9:17 Ross Dickson
2003-12-21 16:29 ` Craig Bradney
2003-12-22 18:50 ` Daniel Drake
2003-12-22 23:56 ` Ross Dickson
2003-12-24 15:41 ` Daniel Drake
2003-12-24 17:49 ` really bensoo_at_soo_dot_com [this message]
2004-02-07 14:55 ` Nforce2 apic timer ack delay Jamie Lokier
2004-02-08 11:41 ` Ross Dickson
2004-02-09 12:33 ` Jamie Lokier
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=20031224124944.A1004@Sophia.soo.com \
--to=lnx-kern@soo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@datscreative.com.au \
/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
Powered by JetHome