Date: Wed, 3 Apr 1996 10:12:10 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: dave@persprog.com (David Alderman) Cc: freebsd-hardware@FreeBSD.ORG, cschuber@orca.gov.bc.ca Subject: Re: Parity Errors Message-ID: <199604030042.KAA16695@genesis.atrad.adelaide.edu.au> In-Reply-To: <76BBE93DA1@novell.persprog.com> from "David Alderman" at Apr 2, 96 11:25:21 am
next in thread | previous in thread | raw e-mail | index | archive | help
David Alderman stands accused of saying: > > > > 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. Yup, yup and it wouldn't surprise me 8) > Has anyone seen parity on the cache? Not on a PC motherboard... > 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. No; according to Solari it isn't, but IOCHCHK is just as bad (one of the spurious-NMI boards I have generates these too - I think it must just be bored...) > Dave Alderman -- dave@persprog.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?199604030042.KAA16695>