From owner-freebsd-current  Mon Dec 13  0: 1:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 4E5E314D16
	for <freebsd-current@FreeBSD.ORG>; Mon, 13 Dec 1999 00:01:53 -0800 (PST)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id JAA33383;
	Mon, 13 Dec 1999 09:01:37 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199912130801.JAA33383@freebsd.dk>
Subject: Re: Errors from the ata disk driver
In-Reply-To: <14418.39524.290684.380673@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 11, 1999 01:43:13 pm"
To: gallatin@cs.duke.edu (Andrew Gallatin)
Date: Mon, 13 Dec 1999 09:01:37 +0100 (CET)
Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Andrew Gallatin wrote:
>  > These are UDMA CRC errors, if you upgrade to the latest current, ata
>  > knows to retry these, only if they persist, something is wrong.
>  > However it could indicate cable problems, ie bad connectors or maybe
>  > too long cables..
>  > 
> 
> He said the disk was attached to a Promise Ultra/33.  Does the
> backdown to PIO on Promise Ultra controllers work now?  I've been
> watching the commits to the ata driver, and haven't seen anything that
> makes me think that it would.. but I haven't tried it since last week.

I've fixed it here (I hope), and it will be in the next batch of fixes.
I hope to get through my mailbox today :)

-Søren


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