From owner-freebsd-hackers Mon Apr 3 22:28:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA03621 for hackers-outgoing; Mon, 3 Apr 1995 22:28:52 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA03615 for ; Mon, 3 Apr 1995 22:28:49 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id VAA06178; Mon, 3 Apr 1995 21:28:19 -0700 From: "Rodney W. Grimes" Message-Id: <199504040428.VAA06178@gndrsh.aac.dev.com> Subject: Re: NMI message To: dgy@seagull.rtd.com (Don Yuniskis) Date: Mon, 3 Apr 1995 21:28:19 -0700 (PDT) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199504040353.UAA24847@seagull.rtd.com> from "Don Yuniskis" at Apr 3, 95 08:53:38 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1105 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Greetings! > My 1.1.5.1R system gasped: > NMI... going to debugger > kernel: type 19 trap, code=0 > shall I assume this was an intermittent parity error (system had been > up for 40 days or so...) like maybe a Vcc glitch or alpha particle, etc.? > Haven't dug out any schematics, etc. but I suspect parity is the only > thing that would yank on NMI (looked like CPU was doing a memory to memory > transfer at the time ... possibly faulting in a page, etc.) > Thx, --don Yes, if this is a once in 40 day event I would attribute it to either an alpha particle or the phase of the moon. If you see any more of them be warry for failing components. If you have a good DVM check your +5V, even better check it for noise with a scope. Check it at the Simms and at the power supply connector to the motherboard. If your simms have tin instead of gold connectors on them reseat them, I have seen a problem here too many times to mention. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD