From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 random lockups - still no solution ?
Date: Sat, 8 Nov 2003 02:34:09 -0500 [thread overview]
Message-ID: <20031108073409.GA7970@forming> (raw)
In-Reply-To: <1068234006.3fabf5162fd7b@horde.sandall.us>
On approximately Fri, Nov 07, 2003 at 11:40:06AM -0800, Eric Sandall wrote:
> Quoting Samuel Kvasnica <samuel.kvasnica@tuwien.ac.at>:
> > It was local APIC ! After recompiling 2.4.22 without local apic
> > everything works smoothly since several weeks. I wonder when there'll
> > be a kernel
> > patch that really solves these nforce2/amd issues.
> > Sam
>
> Disabling local APIC on 2.6.0-test9-mm2 also fixes this (I haven't tried on
> earlier kernels).
>
> -sandalle
>
I am seeing the same thing here. Disk activity and APIC don't seem to
do well. What kind of performance hit if any are we taking by disabling
APIC?
--
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
prev parent reply other threads:[~2003-11-08 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 18:01 nforce2 random lockups - still no solution ? Samuel Kvasnica
2003-10-21 18:13 ` Matt H.
2003-10-22 8:54 ` Vitez Gabor
2003-10-22 13:27 ` Samuel Kvasnica
[not found] ` <3F96847C.4000506@tuwien.ac.at>
[not found] ` <20031022133327.GA25283@swszl.szkp.uni-miskolc.hu>
2003-10-23 10:17 ` Samuel Kvasnica
2003-10-23 10:48 ` Mikael Pettersson
2003-10-23 11:04 ` Samuel Kvasnica
2003-10-23 12:51 ` James Courtier-Dutton
2003-11-05 23:11 ` Denis
2003-11-06 10:45 ` Samuel Kvasnica
2003-11-07 19:40 ` Eric Sandall
2003-11-08 7:34 ` Josh McKinney [this message]
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=20031108073409.GA7970@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 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.