Return to BSD News archive
Newsgroups: comp.unix.bsd.netbsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.dacom.co.kr!usenet.seri.re.kr!news.cais.net!xara.net!SoNet!rmplc!yama.mcc.ac.uk!keele!peer-news.britain.eu.net!newsfeed.ed.ac.uk!dcs.ed.ac.uk!not-for-mail From: st@epcc.ed.ac.uk (Scott Telford) Subject: Re: What does this mean? X-Nntp-Posting-Host: amber.epcc.ed.ac.uk Message-ID: <DMIFKo.8CM.0.staffin.dcs.ed.ac.uk@dcs.ed.ac.uk> Sender: cnews@dcs.ed.ac.uk (UseNet News Admin) Organization: Edinburgh Parallel Computing Centre, University of Edinburgh, UK. X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] References: <umar-0502960901340001@dial1-10.cybercom.net> Date: Fri, 9 Feb 1996 13:17:09 GMT Lines: 20 In article <umar-0502960901340001@dial1-10.cybercom.net>, Rob Landry (umar@cybercom.net) wrote: > My 386 running NetBSD 1.1/i386 occasionally displays the following message: > > natrix/netbsd: NMI port 61 b0, port 70 ff > > I know that NMI stands for non-maskable interrupt, but what exactly is > this message telling me and (more important) what are the practical > consequences? It usually means your PC detected a RAM parity error. Don't be surprised if it behaves oddly or crashes after one of these messages. NetBSD shows the status of port 0x61 when it gets an NMI because one bit of the port is a flag which indicates that the "trigger NMI on parity error" behaviour is enabled, but I can't remember which one.... -- Scott Telford, Edinburgh Parallel Computing Centre, <s.telford@ed.ac.uk> University of Edinburgh, Mayfield Rd, Edinburgh, EH9 3JZ, UK.(+44 131 650 5978) "Is it a virus, a drug, or a religion?" "What's the difference?" (Snow Crash)