From owner-freebsd-current  Wed Dec 15 10: 3: 7 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 21A8C150E4; Wed, 15 Dec 1999 10:03:03 -0800 (PST)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id TAA65973;
	Wed, 15 Dec 1999 19:01:59 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199912151801.TAA65973@freebsd.dk>
Subject: Re: HEADSUP: wd driver will be retired!
In-Reply-To: <Pine.BSF.3.96.991215113708.20990C-100000@fledge.watson.org> from Robert Watson at "Dec 15, 1999 11:49:56 am"
To: robert+freebsd@cyrus.watson.org (Robert Watson)
Date: Wed, 15 Dec 1999 19:01:59 +0100 (CET)
Cc: peter@netplex.com.au (Peter Wemm), grog@lemis.com (Greg Lehey),
	msmith@FreeBSD.ORG (Mike Smith), gchil0@pop.uky.edu (Greg Childers),
	phk@critter.freebsd.dk (Poul-Henning Kamp), 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 Robert Watson wrote:
> On Tue, 14 Dec 1999, Peter Wemm wrote:
> 
> > The RZ1000 is *dangerous*!  We are doing no favours by making it run.. :-/
> > IMHO It is better to loose the user by not playing ball than to corrupt
> > their data or run unreliably and make them hate us for it.
> > 
> > http://www.faqs.org/faqs/pc-hardware-faq/enhanced-IDE/part1/

Amen!
 
> Since someone has code to detect these, how about putting this code in the
> ata driver probe so it can say something appropriately obscene and we
> start getting feedback about how widely deployed they are, and so that
> users can evaluate their risk in using the new driver?  There's also
> mention of being able to disable features in the bios to fix this--is this
> a workaround that can be initiated from user software in a useful way?
> I.e., if the ata driver detects bad hardware, it pulls in a loadable
> kernel module that would somehow address the problem, or avoids the issues
> which cause corruption, if identifiable?

That particular chip is so broken in so obscure ways, that most of the
"fixes" floating around doesn't. Its just plain broken, and should be
avoided totally and at all cost...

-Søren


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