Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 26 Feb 2003 11:26:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 26 Feb 2003 11:26:02 -0500 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:24120 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Wed, 26 Feb 2003 11:26:01 -0500 From: Alan Cox Message-Id: <200302261636.h1QGaAv21387@devserv.devel.redhat.com> Subject: Re: Tighten up serverworks workaround. To: davej@codemonkey.org.uk (Dave Jones) Date: Wed, 26 Feb 2003 11:36:10 -0500 (EST) Cc: alan@redhat.com (Alan Cox), torvalds@transmeta.com, linux-kernel@vger.kernel.org In-Reply-To: <20030226162944.GA15163@codemonkey.org.uk> from "Dave Jones" at Feb 26, 2003 04:29:44 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1019 Lines: 24 > I've reports of people with rev6's who have reported success > with that workaround commented out. Could be they never > pushed the machine hard enough to trigger a bug, but I'd > have thought this breakage would show up pretty quickly. It doesn't. It requires the right patterns and took Dell quite some time to identify and pin down. If its like the 450NX one which I suspect it is then you have to have pending misordered stores to a write gathering target evicted by another read. > My attempts to contact serverworks in the past have fallen on > deaf ears. maybe you have better luck ? I'll try. I got on ok with them for the OSB4 stuff but thats a long time ago and they've been eaten since then [Bcc'd to the person I suspect is the right starting point] Alan - 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/