From owner-freebsd-hardware Tue Apr 2 08:31:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07006 for hardware-outgoing; Tue, 2 Apr 1996 08:31:02 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA07001 for ; Tue, 2 Apr 1996 08:30:56 -0800 (PST) Received: by persprog.com (8.7.5/4.10) id LAA23718; Tue, 2 Apr 1996 11:27:28 -0500 Received: from novell(192.2.2.201) by cerberus.ppi.com via smap (V1.3) id sma023716; Tue Apr 2 11:27:23 1996 Received: from NOVELL/SpoolDir by novell.persprog.com (Mercury 1.12); Tue, 2 Apr 96 11:25:28 +0500 Received: from SpoolDir by NOVELL (Mercury 1.12); Tue, 2 Apr 96 11:25:22 +0500 From: "David Alderman" Organization: Personalized Programming, Inc. To: freebsd-hardware@FreeBSD.org, cschuber@orca.gov.bc.ca Date: Tue, 2 Apr 1996 11:25:21 EST Subject: Re: Parity Errors Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <76BBE93DA1@novell.persprog.com> Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > FreeBSD can't generate NMI signals; it's your motherboard hardware that's > doing that. It wouldn't surprise me if Linux just ignored them 8) > I've seen NMI's come out of motherboards from problems other than main RAM. Sometimes noise or other problems can cause NMI's with poor motherboard designs. I seem to remember stray DMA requests can sometimes trigger an NMI. Has anyone seen parity on the cache? It's probably not FreeBSD to blame - it is more likely FreeBSD is revealing a latent weakness in your system. Does anyone remember if NMI is brought out to the ISA bus? This would open up all kinds of possibilities. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ======================================