Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 26 Feb 2003 13:38:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 26 Feb 2003 13:38:21 -0500 Received: from mail.coastside.net ([207.213.212.6]:41697 "EHLO mail.coastside.net") by vger.kernel.org with ESMTP id ; Wed, 26 Feb 2003 13:38:20 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <200302261803.h1QI3BT24020@devserv.devel.redhat.com> References: <200302261803.h1QI3BT24020@devserv.devel.redhat.com> Date: Wed, 26 Feb 2003 10:47:52 -0800 To: Alan Cox , kimball@serverworks.com (Kimball Brown) From: Jonathan Lundell Subject: Re: Tighten up serverworks workaround. Cc: alan@redhat.com (Alan Cox), davej@codemonkey.org.uk, torvalds@transmeta.com, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 927 Lines: 20 At 1:03pm -0500 2/26/03, Alan Cox wrote: > > How can e help? Please give me a configuration and how the bug manifests >> inself. > >OSB4 chipset system, some memory areas marked write combining with the >processor memory type range registers. A long time ago Dell (I >think) reported corruption from this and submitted changes to block the >use of write combining on OSB4. The question has arisen as to whether >thats a known thing, and if so which release of the chipset fixed it so that >people can only apply such a restriction to problem cases not all OSB4. Presumably we're talking about CNB30 (the north bridge) rather than OSB4 (the south bridge). -- /Jonathan Lundell. - 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/