From owner-freebsd-hardware  Tue Apr  2 04:09:41 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA11087
          for hardware-outgoing; Tue, 2 Apr 1996 04:09:41 -0800 (PST)
Received: from fire.dkrz.de (fire.dkrz.de [136.172.110.250])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA11072
          for <freebsd-hardware@FreeBSD.org>; Tue, 2 Apr 1996 04:09:33 -0800 (PST)
Received: from racer.dkrz.de (racer.dkrz.de [136.172.110.55]) by fire.dkrz.de (8.7.5/8.7.3) with ESMTP id OAA14355; Tue, 2 Apr 1996 14:08:30 +0200 (MET DST)
Received: (from gwk@localhost) by racer.dkrz.de (8.7.4/8.7.3) id OAA15017; Tue, 2 Apr 1996 14:06:05 +0200 (MET DST)
Date: Tue, 2 Apr 1996 14:06:05 +0200 (MET DST)
Message-Id: <199604021206.OAA15017@racer.dkrz.de>
From: "Georg-W. Koltermann" <gwk@racer.dkrz.de>
To: msmith@atrad.adelaide.edu.au
CC: cschuber@orca.gov.bc.ca, freebsd-hardware@FreeBSD.org
In-reply-to: <199604020145.LAA08833@genesis.atrad.adelaide.edu.au> (message
	from Michael Smith on Tue, 2 Apr 1996 11:15:29 +0930 (CST))
Subject: Re: Parity Errors
Reply-to: gwk@cray.com
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> From: Michael Smith <msmith@atrad.adelaide.edu.au>
> Date: Tue, 2 Apr 1996 11:15:29 +0930 (CST)
> Cc: freebsd-hardware@FreeBSD.org
>> 
> Cy Schubert - ITSD Open Systems Group stands accused of saying:
> 
> ...
>
> > I can configure the machine for memory and/or cache read or write
> > wait states independently.  Should I add a wait state and where,
> > memory or cache, read or write?
> 
> If you can disable parity checking with your BIOS, do that.  ...

Huh?  Why would THAT be a good idea?

I at least prefer to get the error message and abort instead of
silently continuing with false data!!!

Regards,

Georg-W. Koltermann, gwk@cray.com