From owner-freebsd-stable Wed Jan 8 6:12: 1 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C82037B401 for ; Wed, 8 Jan 2003 06:11:59 -0800 (PST) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD1FA43EA9 for ; Wed, 8 Jan 2003 06:11:58 -0800 (PST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp2.sentex.ca (8.12.6/8.12.6) with ESMTP id h08EBqOw077720; Wed, 8 Jan 2003 09:11:52 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.6/8.12.6) with ESMTP id h08EEEHY099641; Wed, 8 Jan 2003 09:14:14 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030108091446.05ae8730@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 08 Jan 2003 09:15:13 -0500 To: Janet Sullivan , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: ATA corruption in DMA mode In-Reply-To: <3E1C302F.6697A823@cox.net> References: <3E1C2EA6.18C86871@vzavenue.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (lava/20020517) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can you boot with a 4.6 kernel now and test it again to confirm the problem really does go away ? ---Mike At 07:05 AM 08/01/2003 -0700, Janet Sullivan wrote: >P.S. I've seen absolutely no ata error messages (command timeout, >etc.). > >Janet Sullivan wrote: > > > > If I copy large (500 meg) files between directories with DMA on, the > > copy becomes corrupt. If I turn DMA off and use PIO mode, the copy is > > fine. Smaller files do not seem to trigger this problem. I am using > > STABLE from a couple of days ago, although I think I may have been > > having this problem for a longer time. I have a Soyo KT333 Platinum > > Dragon motherboard with a built in Highpoint IDE raid controller. The > > corruption happens on my ar0 array, which is RAID 1 and consists of two > > Western Digital 40g drives. fsck has never found any problems with > > these drives. I'm using 80-pin cables, and the array used to run clean > > (around 4.6 and before). > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message