Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!usc!apple!uokmax!munnari.oz.au!metro!ipso!runxtsa!brucee
From: brucee@runxtsa.runx.oz.au (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: MINIX 1.5.10 ignores NMI on Intel machines?
Keywords: NMI
Message-ID: <2176@runxtsa.runx.oz.au>
Date: 18 Aug 90 08:35:44 GMT
References: <1990Aug16.021356.24004@dsuvax.uucp>
Organization: RUNX Unix Timeshare.  Sydney, Australia.
Lines: 15

In article <1990Aug16.021356.24004@dsuvax.uucp> ghelmer@dsuvax.uucp (Guy Helmer) writes:
>My beef is: I though MINIX would have panic'ed as fast as possible on
>receipt of NMI, which at least on XT-class machines means parity trouble.
>There is no way an operating system should continue if this condition
>occurs.

An NMI in kernel+mm+fs causes a panic.

An NMI in a user program just causes a core dump. Unless it is INIT or a shell
that gets killed, the shell normally prints a message and you have the system
alive to help find the error.
-- 
Bruce Evans
Internet: brucee@runxtsa.runx.oz.au    UUCP: uunet!runxtsa.runx.oz.au!brucee
(My other address (evans@ditsyda.oz.au) no longer works)