From owner-freebsd-stable Fri Nov 24 18:54:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from poseidon.cannoncreek.com (unknown [216.252.208.241]) by hub.freebsd.org (Postfix) with ESMTP id 9B90737B4CF for ; Fri, 24 Nov 2000 18:54:30 -0800 (PST) Received: from nomad (nomad.cannoncreek.com [192.168.0.69]) by poseidon.cannoncreek.com (8.9.3/8.9.3) with SMTP id KAA32336; Sat, 25 Nov 2000 10:54:59 +0800 (PHT) (envelope-from marsattack@cannoncreek.com) Message-ID: <006301c0568d$25feb1c0$4500a8c0@nomad> From: "Mars Attack" To: "Janet Sullivan" , References: <3A1EDCCA.267A6FD3@techie.com> Subject: Re: ata0 problems Date: Sat, 25 Nov 2000 11:09:30 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was getting ad0: WRITE command timeout errors on a Quantum drive & > ASUS TX97 mobo regularly. I switched the drive to pio mode, which > stopped the error messages, but a couple weeks later the drive died > completely (won't even spin up). I'd say that if anyone is seeing WRITE > command timeout errors it might be a good time to stick the drive in pio > mode and make a backup "just in case". ;-) > Try upgrading to 4.2-Stable. If you already have, you might want to address your concerns to Soren, the ATA guru sos@freebsd.dk. There were some problems with the code for ATA-UDMA 66 drives. There was even a problem that went on for 2 months about UDMA-66 set as slave; but it's fixed in 4.2R as far as I can tell on my machines. see http://www.freebsd.org/cgi/query-pr.cgi?pr=22634 > Thierry.Herbelot@alcatel.fr wrote: > > > > Hello, > > > > I also have seen it with 4.1-R and 4.1.1-R with a BX motherboard : in my case, it's most likely > > due to bad hard disks (which the ata(4) driver is using with all performance options "ON") > > > > TfH > > > > Grigoriy Strokin on 24/11/2000 08:37:08 > > > > > > > > To: "Corey G." > > > > cc: Michael , > > freebsd-stable@FreeBSD.ORG(bcc: Thierry > > HERBELOT/FR/ALCATEL) > > > > > > > > Subject: Re: ata0 problems > > > > > > I haven't tried FreeBSD 4.2 yet, but I had > > this problem in 4.0 and 4.1, and described > > it in http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17643. > > > > The problem report has been recently closed > > with the reason: > > Problems with the VIA 586 chipset should be fixed in 4.2 and later > > > > So it seems it should be re-opened? > > > > On Thu, Nov 23, 2000 at 07:24:01PM -0600, Corey G. wrote: > > > I saw the same error tonight. (if it is an error). > > > > > > FreeBSD 4.2 > > > AMD K62-450 > > > ATA-66 - Maxtor Drive > > > > > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > > ata0: resetting devices .. done > > > ad0: WRITE command timeout tag=0 serv=0 - resetting > > > ata0: resetting devices .. done > > > > > > On Thu, Nov 23, 2000 at 06:30:11PM +0000, Michael wrote: > > > > Hello > > > > I have problems in FreeBSD 4.2-STABLE > > > > > > > > > > > > Nov 23 09:49:53 lucky /kernel: ata0: resetting devices .. done > > > > Nov 23 09:50:44 lucky /kernel: ad0: WRITE command timeout tag=0 serv=0 - > > > > resetting > > > > > > > > regards, Michael > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-stable" in the body of the message > > > ---end quoted text--- > > > > > > -- > > > Best Regards, > > > Corey > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Cheers .marz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message