From owner-freebsd-current Tue Mar 5 11:53:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18850 for current-outgoing; Tue, 5 Mar 1996 11:53:01 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA18831 Tue, 5 Mar 1996 11:52:56 -0800 (PST) Message-Id: <199603051952.LAA18831@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: imb@scgt.oz.au (michael butler), stable@FreeBSD.org, current@FreeBSD.org Subject: Re: 2842 and the disappearing file-system :-( In-reply-to: Your message of "Tue, 05 Mar 1996 11:12:04 MST." <199603051812.LAA08681@phaeton.artisoft.com> Date: Tue, 05 Mar 1996 11:52:56 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk >> This particular failure, as I mentioned before on the -stable list, is >> specific to the VESA controller (2842 rev C). It has never occurred with the >> BT542B and I've established that the "cheap" version (i.e. non-enhanced) of >> the Amd486DX4 that I'm using is only capable of running its internal cache >> in write-thru mode. >> >> My question is this .. since -stable is presently unusable unless I want to >> strangle my disk I/O (with news arriving at ~3 articles/second) and -release >> too buggy for "heavy-duty" use, is -current likely to be any better ? > >Obviously your cache is not being updated correctly as a result of >a DMA completion. > Actually this appears to be a bug in eisaconf as it affects all eisa scsi controllers at the moment. I'm looking into it, but the problem is not obvious and doesn't occur in -current. > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================