Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!news.sgi.com!newsfeed.nacamar.de!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: PANIC WHY Date: 7 Mar 1997 00:15:52 GMT Organization: Private BSD site, Dresden Lines: 21 Message-ID: <5fnmno$282@uriah.heep.sax.de> References: <5fmji4$rpc@news.nl.compuware.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36716 Kuiper.Marcel@uniface.nl (Marcel Kuiper) wrote: > panic: Memory Parity Error: possibly hardware failure > > Now I haven't got memory with parity bits, and in my BIOS the parity > check option is disabled. Are there any more possible causes that can > throw up this message. There's also an ISA bus line for it (IOCHCK). It's normally supposed to be distinguishable from a memory parity error, but if the chipset has botched this, there's a chance that it will be misinterpreted. I've also seen a notebook where NMI is raised at a powerfail. (See options ``POWERFAIL_NMI''.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)