From owner-freebsd-current@FreeBSD.ORG  Fri Oct  1 11:01:30 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B427B16A4CE
	for <freebsd-current@freebsd.org>;
	Fri,  1 Oct 2004 11:01:30 +0000 (GMT)
Received: from mail1.infoeng.flinders.edu.au (mail1.ist.flinders.edu.au
	[129.96.1.66])	by mx1.FreeBSD.org (Postfix) with ESMTP id 84DB643D3F
	for <freebsd-current@freebsd.org>;
	Fri,  1 Oct 2004 11:01:29 +0000 (GMT)
	(envelope-from tris@infoeng.flinders.edu.au)
Received: from rhino (rhino.infoeng.flinders.edu.au [129.96.1.189])
	i91B1Sm09137	for <freebsd-current@freebsd.org>;
	Fri, 1 Oct 2004 20:31:28 +0930 (CST)
Date: Fri, 1 Oct 2004 20:31:23 +0930
From: Tristan <tris@infoeng.flinders.edu.au>
To: freebsd-current@freebsd.org
Message-Id: <20041001203123.65b94c6f@rhino>
In-Reply-To: <415CAF59.5070107@FreeBSD.org>
References: <20041001093515.5cd51b2d@rhino>
	<20041001005227.GA28811@electra.cse.Buffalo.EDU>
	<20041001102816.5b14b79f@rhino>
	<415CAF59.5070107@FreeBSD.org>
X-Mailer: Sylpheed version 0.9.11claws (GTK+ 1.2.10; sparc-sun-solaris2.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2004 11:01:30 -0000

On Thu, 30 Sep 2004 19:14:01 -0600
Scott Long <scottl@FreeBSD.org> wrote:
> Tristan wrote:
> > On Thu, 30 Sep 2004 20:52:27 -0400
> > Ken Smith <kensmith@cse.Buffalo.EDU> 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 <ST315310A/3.28> [29651/16/63] at ata2-master UDMA66
> >>>acd0: CDRW <LTN486S/YSU1> at ata2-slave PIO4
> >>>ata3-master: DMA limited to UDMA33, non-ATA66 cable or device
> >>>ad1: 39266MB <IBM-DTLA-305040/TW4OA60A> [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.
> > 
> > 
> > nope, its only on ad0. ad1 seems to be fine, however it is hardly used.
> 
> What happens if you remove the CDROM from the ad0 chain?
> 
> Scott

I still get the errors with the CDROM removed. Perhaps the cable needs
replacing? thats what these symptoms say to me.

tris