From owner-freebsd-stable  Sat Dec 29  0: 2: 1 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from shark.amis.net (shark.amis.net [212.18.32.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id ECD8D37B421; Sat, 29 Dec 2001 00:01:55 -0800 (PST)
Received: from baracuda.amis.net (baracuda.amis.net [212.18.32.4])
	by shark.amis.net (Postfix) with ESMTP
	id BC6137D23; Sat, 29 Dec 2001 09:01:54 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by baracuda.amis.net (Postfix) with ESMTP
	id 35E479B0C; Sat, 29 Dec 2001 09:01:54 +0100 (CET)
Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5])
	by baracuda.amis.net (Postfix) with ESMTP
	id E4D109B08; Sat, 29 Dec 2001 09:01:52 +0100 (CET)
Received: by titanic.medinet.si (Postfix, from userid 1000)
	id 1D01E55411; Sat, 29 Dec 2001 09:01:49 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by titanic.medinet.si (Postfix) with ESMTP
	id 144AC55404; Sat, 29 Dec 2001 09:01:49 +0100 (CET)
Date: Sat, 29 Dec 2001 09:01:49 +0100 (CET)
From: Blaz Zupan <blaz@si.FreeBSD.org>
X-X-Sender:  <blaz@titanic.medinet.si>
To: Eugene Grosbein <eugen@svzserv.kemerovo.su>
Cc: <qa@freebsd.org>, <stable@freebsd.org>
Subject: Re: 4.5-PRERELEASE (25 Dec) and IBM IC35L040AVER07-0
In-Reply-To: <3C2D30F8.DA84A007@svzserv.kemerovo.su>
Message-ID: <20011229085953.R81588-100000@titanic.medinet.si>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS perl-10
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

> > You have a UDMA33-only controller, but a UDMA100-capable drive. This could be
> > the reason for the problems.
>
> How can this produce problems?

Drive runs at UDMA100 (for whatever reason), while controller and OS negotiate
UDMA33. I've not seen something like this happen with UDMA100, but I *have*
seen it with a UDMA66 drive on a UDMA33 controller. I believe it was a Fujitsu
UDMA66 drive where I saw this. It was some time ago, so my memory may be
sketchy.


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