From owner-freebsd-current@FreeBSD.ORG Fri Oct 1 01:28:57 2004 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 565E716A4CE for ; Fri, 1 Oct 2004 01:28:57 +0000 (GMT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8E9543D54 for ; Fri, 1 Oct 2004 01:28:56 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) i911Sh1f096068; Fri, 1 Oct 2004 03:28:45 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id i911Scxp096067; Fri, 1 Oct 2004 03:28:38 +0200 (CEST) (envelope-from marius) Date: Fri, 1 Oct 2004 03:28:38 +0200 From: Marius Strobl To: Tristan Message-ID: <20041001032838.A88228@newtrinity.zeist.de> References: <20041001093515.5cd51b2d@rhino> <20041001005227.GA28811@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20041001005227.GA28811@electra.cse.Buffalo.EDU>; from kensmith@cse.Buffalo.EDU on Thu, Sep 30, 2004 at 08:52:27PM -0400 X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.27.0.12; VDF 6.27.0.82 (host: newtrinity.zeist.de) cc: Ken Smith cc: freebsd-current@freebsd.org Subject: Re: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=xxx 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, 01 Oct 2004 01:28:57 -0000 On Thu, Sep 30, 2004 at 08:52:27PM -0400, Ken Smith wrote: > On Fri, Oct 01, 2004 at 09:35:15AM +0930, Tristan wrote: > > > FreeBSD 6.0-CURRENT with GENERIC kernel built 27th Sep. > > On a SunBlade 100 I see these messages regularly when > > dma is enabled. The messages go away when I either use > > atacontrol to set the mode to PIO4 or set hw.ata.ata_dma to 0 > > I do get data corruption on the disk if left in DMA mode. > > Just FYI my primary test machine is a SunBlade 100, it seems to > be doing OK with a kernel built from this morning's source. I've > been doing most of my builds from an NFS server though, I'll do > a check with a full buildworld which will use the local drive more. > > > ad0: 14594MB [29651/16/63] at ata2-master UDMA66 > > acd0: CDRW at ata2-slave PIO4 > > ata3-master: DMA limited to UDMA33, non-ATA66 cable or device > > ad1: 39266MB [79780/16/63] at ata3-master UDMA33 > > Mounted root from ufs:/dev/ad0a. > > Is the data corruption spread across both drives, or just ad1? That > message about the cable or device being limited could be a clue. > Did you replace the cable of the primary channel? AFAIK on Blade 100 there's a hardware bug that causes data corruption when using UDMA66 and Sun ships them with a 40-pin cable as sort of a work-around. So these non-ATA66 cable messages should be rather normal on Blade 100. Not all revisions might be affected though.