Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932666AbXARWxc (ORCPT ); Thu, 18 Jan 2007 17:53:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932697AbXARWxc (ORCPT ); Thu, 18 Jan 2007 17:53:32 -0500 Received: from mx2.suse.de ([195.135.220.15]:58566 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932666AbXARWxb (ORCPT ); Thu, 18 Jan 2007 17:53:31 -0500 From: Andi Kleen To: Chip Coldwell Subject: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?) Date: Fri, 19 Jan 2007 09:49:47 +1100 User-Agent: KMail/1.9.1 Cc: Chris Wedgwood , Christoph Anton Mitterer , Robert Hancock , linux-kernel@vger.kernel.org, knweiss@gmx.de, andersen@codepoet.org, krader@us.ibm.com, lfriedman@nvidia.com, linux-nforce-bugs@nvidia.com References: <200701180915.32944.ak@suse.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701190949.48404.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 945 Lines: 22 On Friday 19 January 2007 08:57, Chip Coldwell wrote: > But it still might be a reasonable thing to do to test the theory that > the problem is cache coherency across the graphics aperture, even if > it isn't a long-term solution for the problem. I suspect it would disturb timing so badly that it might hide the original problem. If that is true then adding udelays might hide it too. Ok i guess you could test with a UP kernel. There change_page_attr should be much cheaper because it doesn't need to IPI to other CPUs. Also use a .2.6.20-rc* kernel that uses CLFLUSH in there, not WBINVD which is also very costly. Anyways I guess we can just wait what the hardware people figure out. -Andi - 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/