From owner-freebsd-questions  Thu May 18 13:12:11 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14])
	by hub.freebsd.org (Postfix) with ESMTP id D850337B51E
	for <questions@FreeBSD.ORG>; Thu, 18 May 2000 13:12:06 -0700 (PDT)
	(envelope-from andymac@bullseye.apana.org.au)
Received: from bullseye.apana.org.au (uucp@localhost)
	by posgate.acis.com.au (8.9.3/8.9.3) with UUCP id GAA16875;
	Fri, 19 May 2000 06:11:56 +1000
Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245])
	by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id WAA00980;
	Thu, 18 May 2000 22:34:17 +1000 (EST)
	(envelope-from andymac@bullseye.apana.org.au)
Date: Thu, 18 May 2000 22:29:02 +1000 (EST)
From: Andrew MacIntyre <andymac@bullseye.apana.org.au>
To: andrew@ugh.net.au
Cc: questions@FreeBSD.ORG
Subject: Re: Yet more HD trouble (ad0: WRITE command timeout - resetting)
In-Reply-To: <Pine.BSF.4.21.0005172239420.26145-100000@starbug.ugh.net.au>
Message-ID: <Pine.OS2.3.95.1000518222511.704A-100000@CENTRAL>
X-X-Sender: andymac@bullseye.apana.org.au
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 17 May 2000 andrew@ugh.net.au wrote:

> It seems wherever I go disks fail before me...anyway I am getting the
> following errors from the kernel:
> 
> ad0: WRITE command timeout - resetting
> ata0: resetting devices .. done
> dc0: TX underrun -- increasing TX threshold
> ad0: WRITE command timeout - resetting
> ata0: resetting devices .. done
> ad0: WRITE command timeout - resetting
> ata0: resetting devices .. done
> ad0: WRITE command timeout - resetting
> ata0: resetting devices .. done
> 
> I dont think the TX underrun error is anything to worry about (although
> I'm not exactly sure what it means) but how about the ata0 messages?
> 
> I'm running 4.0-STABLE as of today. From dmesg:
> 
> <snip>
> 
> CPU: Pentium Pro (179.63-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0x619  Stepping = 9
> Features=0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV>
> real memory  = 33554432 (32768K bytes)
> 
> <snip>
> 
> Correcting Natoma config for non-SMP
> Correcting Natoma config for non-SMP
> dc0: <Intel 21143 10/100BaseTX> port 0xec00-0xec7f mem
> 0xfdffbc00-0xfdffbc7f irq
>  9 at device 3.0 on pci0
> dc0: Ethernet address: 00:00:f8:77:4c:d3
> miibus0: <MII bus> on dc0
> nsphy0: <DP83840 10/100 media interface> on miibus0
> nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> isab0: <Intel 82371SB PCI to ISA bridge> at device 7.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel PIIX3 ATA controller> port 0xecf0-0xecff at device 7.1 on
> pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> 
> <snip>
> 
> ad0: 3079MB <QUANTUM FIREBALL ST3.2A> [6256/16/63] at ata0-master using
> WDMA2
> acd0: CDROM <TOSHIBA CD-ROM XM-6002B> at ata1-master using PIO3

Have you tried derating ad0 to PIO4?  ISTR some patchiness of reliability
with PIIX3 controllers and DMA, though -STABLE has had fixes applied to
the ata driver.

--
Andrew I MacIntyre                     "These thoughts are mine alone..."
E-mail: andrew.macintyre@aba.gov.au    (work) | Snail: PO Box 370
        andymac@bullseye.apana.org.au  (play) |        Belconnen  ACT  2616
        andymac@pcug.org.au           (play2) |        Australia



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message