Date: Tue, 2 Apr 1996 22:20:55 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: gwk@cray.com Cc: msmith@atrad.adelaide.edu.au, cschuber@orca.gov.bc.ca, freebsd-hardware@FreeBSD.org Subject: Re: Parity Errors Message-ID: <199604021250.WAA14688@genesis.atrad.adelaide.edu.au> In-Reply-To: <199604021206.OAA15017@racer.dkrz.de> from "Georg-W. Koltermann" at Apr 2, 96 02:06:05 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Georg-W. Koltermann stands accused of saying: > > > > If you can disable parity checking with your BIOS, do that. ... > > Huh? Why would THAT be a good idea? Because the machine will keep going. I have at least one, possibly two systems here that generate spurious NMI's on a regular basis. If the system subsequently fails to work happily, there's some other problem. One step at a time... (FWIW, both of the offending systems 'make world' quite happily, although one has no provision for disabling NMI in the BIOS and thus requires one to continue from ddb.) > I at least prefer to get the error message and abort instead of > silently continuing with false data!!! 'tall depends on where the real error is I guess 8) > Georg-W. Koltermann, gwk@cray.com -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604021250.WAA14688>