From owner-freebsd-current Mon Dec 20 9:30:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2B10E153C4 for ; Mon, 20 Dec 1999 09:30:24 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA19852; Mon, 20 Dec 1999 12:30:22 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA12875; Mon, 20 Dec 1999 12:29:51 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Dec 1999 12:29:51 -0500 (EST) To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA: more Promise Ultra wedges In-Reply-To: <199912191632.RAA22826@freebsd.dk> References: <14428.10180.553556.127603@grasshopper.cs.duke.edu> <199912191632.RAA22826@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14430.26201.835683.360880@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > It seems Andrew Gallatin wrote: > >=20 > > S=F8ren, > >=20 > > It looks like I spoke to soon when I said the world was safe for > > Promise Ultra users: > >=20 > > ad3: ad_timeout: lost disk contact - resetting > > ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 6594768ad3: = DMA problem en > > countered, fallback to PIO mode > > ad3: DMA problem encountered, fallback to PIO mode > > done > > ad1: UDMA CRC READ ERROR blk# 10522095 retrying > > ad3: ad_timeout: lost disk contact - resetting > > ata4: resetting devices .. done >=20 > Is the above all info, or is it snipped somehow, its looks a bit wie= rd.. That was snipped directly from a serial console log. Now that I have the machine rebooted, here are the syslog messages from /var/log/messages: Dec 17 17:01:44 waffle /kernel: ad3: ad_timeout: lost disk contact - re= setting Dec 17 17:01:44 waffle /kernel: ata4: resetting devices .. ad3: HARD WR= ITE ERROR blk# 6594768ad3: DMA problem encountered, fallback to PIO mod= e Dec 17 17:01:44 waffle /kernel: ad3: DMA problem encountered, fallback = to PIO mode Dec 17 17:01:44 waffle /kernel: done Dec 17 17:02:09 waffle /kernel: ad1: UDMA CRC READ ERROR blk# 10522095 = retrying Dec 17 17:02:14 waffle /kernel: ad3: ad_timeout: lost disk contact - re= setting Dec 17 17:02:14 waffle /kernel: ata4: resetting devices .. done > > BTW, I'd really like a tunable or some way to prevent a permanent > > fallback to PIO. I'm more than willing to tolerate one hard error= per > > week or so on a disk which sees 10s of gigabytes of data read & > > written between errors. =20 >=20 > Hmm, I'll think about what we can do here... Thanks! That would be greatly appreciated. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message