Date: Tue, 2 Apr 1996 14:06:05 +0200 (MET DST) From: "Georg-W. Koltermann" <gwk@racer.dkrz.de> To: msmith@atrad.adelaide.edu.au Cc: cschuber@orca.gov.bc.ca, freebsd-hardware@FreeBSD.org Subject: Re: Parity Errors Message-ID: <199604021206.OAA15017@racer.dkrz.de> In-Reply-To: <199604020145.LAA08833@genesis.atrad.adelaide.edu.au> (message from Michael Smith on Tue, 2 Apr 1996 11:15:29 %2B0930 (CST))
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604021206.OAA15017>