Date: Sat, 8 Nov 2003 02:34:09 -0500
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 random lockups - still no solution ?
Message-ID: <20031108073409.GA7970@forming>
Mail-Followup-To: linux-kernel@vger.kernel.org
References: <3F95748E.8020202@tuwien.ac.at> <200311060111.06729.vda@port.imtp.ilyichevsk.odessa.ua> <3FAA2653.9020002@tuwien.ac.at> <1068234006.3fabf5162fd7b@horde.sandall.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1068234006.3fabf5162fd7b@horde.sandall.us>
User-Agent: Mutt/1.5.4i
From: Josh McKinney <forming@charter.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1290
Lines: 30

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/