From owner-freebsd-current Wed Dec 15 8:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2B0D8155F2; Wed, 15 Dec 1999 08:51:56 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA21798; Wed, 15 Dec 1999 11:49:56 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 15 Dec 1999 11:49:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Peter Wemm Cc: Greg Lehey , Mike Smith , Greg Childers , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991213234037.36B341CA0@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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/ ... > > In both cases, the corruption occurs only in specific software > environments and is very subtle; you can go on working for months > without suspecting anything more than buggy software. The damage can > be immense. For all the details, look at Roedy Green's (roedy@bix.com) > "PCI EIDE controller flaws" FAQ included with his EIDE test > program which will > test your system for the bugs. > > BE WARNED that you're playing Russian roulette with your data if you > continue working on an affected machine without taking notice of this > problem. 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? Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message