From: Disconnect <lkml@sigkill.net>
To: Craig Bradney <cbradney@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.4] Nforce2 oops and occasional hang (tried the lockups patch, no difference)
Date: Fri, 19 Dec 2003 15:32:32 -0500 [thread overview]
Message-ID: <1071865952.6159.34.camel@slappy> (raw)
In-Reply-To: <1071865339.9969.3.camel@athlonxp.bradney.info>
On Fri, 2003-12-19 at 15:22, Craig Bradney wrote:
> Does this not relate directly to the APIC/IOAPIC issues with 2.6 kernel
> and nforce chipset motherboards?
Not when apic is disabled. (And I'm guessing you mean 2.4, right?
Although IIRC the patches are available for both.)
The patches for enabling/using apic/io-apic on nforce2 work fine, except
instead of oopsing it hardlocks semi-randomly. (It ran fine for a few
days, then hardlocked, and upon reboot it only made it about 10 minutes,
then another 30 minutes, so I went back to an unpatched 2.4.23 with
'noapic'. Now that the hardware has arrived I can move production
elsewhere and do further testing.) I was under the impression that
nmi-watchdog was supposed to prevent the hardlocks (well, turn them into
oopses), but no such luck here.
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-12-19 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 2:25 [2.4] Nforce2 oops and occasional hang (tried the lockups patch, no difference) Ross Dickson
2003-12-13 5:02 ` Bob
2003-12-15 16:40 ` Disconnect
2003-12-18 18:52 ` Disconnect
2003-12-19 17:24 ` Disconnect
2003-12-19 20:22 ` Craig Bradney
2003-12-19 20:32 ` Disconnect [this message]
2003-12-20 12:30 ` Voicu Liviu
-- strict thread matches above, loose matches on Subject: below --
2003-12-11 16:16 Disconnect
2003-12-11 16:38 ` Josh McKinney
2003-12-11 17:19 ` Disconnect
2003-12-11 17:22 ` Disconnect
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=1071865952.6159.34.camel@slappy \
--to=lkml@sigkill.net \
--cc=cbradney@zip.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.