From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266615AbUBLVmE (ORCPT ); Thu, 12 Feb 2004 16:42:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266616AbUBLVmE (ORCPT ); Thu, 12 Feb 2004 16:42:04 -0500 Received: from fed1mtao04.cox.net ([68.6.19.241]:8924 "EHLO fed1mtao04.cox.net") by vger.kernel.org with ESMTP id S266615AbUBLVmB (ORCPT ); Thu, 12 Feb 2004 16:42:01 -0500 Date: Thu, 12 Feb 2004 14:44:07 -0700 From: Jesse Allen To: Derek Foreman Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay. Message-ID: <20040212214407.GA865@tesore.local> Mail-Followup-To: Jesse Allen , Derek Foreman , linux-kernel@vger.kernel.org References: <200402120122.06362.ross@datscreative.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 12, 2004 at 12:17:12PM -0600, Derek Foreman wrote: > Some nforce2 systems work just fine. Is there a way to distinguish > between systems that need it and those that don't? > Some nforce2 systems are fixed in certain bioses. The problem is we don't know where/what it is in the bios. C1 disconnect is a clue. > (if anyone's running a betting pool, my money's on nforce2+cpu with half > frequency multiplier ;) I don't know what your talking about. My Shuttle AN35N nforce2 board can run vanilla kernels with the 12-5-2003 dated bios version and not lock up. The frequencies I run are all the default/standard ones. Jesse