From owner-freebsd-current@FreeBSD.ORG Fri Dec 19 01:08:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44DD416A4CE for ; Fri, 19 Dec 2003 01:08:02 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D5C43D45 for ; Fri, 19 Dec 2003 01:07:58 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hBJ95Gtx086830; Fri, 19 Dec 2003 10:05:16 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hBJ95Gpm086829; Fri, 19 Dec 2003 10:05:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200312190905.hBJ95Gpm086829@spider.deepcore.dk> In-Reply-To: <200312181516.05505.peter@wemm.org> To: Peter Wemm Date: Fri, 19 Dec 2003 10:05:16 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: Ion-Mihai Tetcu cc: freebsd-current@FreeBSD.ORG Subject: Re: 5.2RC1 Read+Write data corruption (with SeagateBarracuda ATAV120G (ST3120023A) + VIA 8237) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 09:08:02 -0000 > Also, it was significantly worse *before* ataNG went in, and its much > worse on RELENG_4 than 5.x for us. Acutally it went away for me on ATAng until I got the AMD64 box. > Something else just occurred to me.. I think all the problems we've > been seeing are on *fast* machines. (p4/xeon/amd64). I wonder if > that is something significant? I'll see if I can confirm this. I think you are pretty much on the money, I've been researching this problem for quite some time (as you know :) ), and I'm pretty confident that it is timing related. However I have not been able to find out exactly where the problem is, and I've tried just about any possible way to changes timing to get a grip on this. However with that nice amd64 box on my shelf it is alot easier to hunt, as that fails reliably :) -Søren Yes I know it works under windows!!