Date: Fri, 13 Jul 2001 13:35:22 -0700 From: "Chad R. Larson" <chad@DCFinc.com> To: Tom <tom@uniserve.com> Cc: Steve Price <steve@havk.org>, stable@FreeBSD.ORG Subject: Re: NMI panics Message-ID: <20010713133522.B14772@freeway.dcfinc.com> In-Reply-To: <Pine.BSF.4.10.10107130920330.47572-100000@athena.uniserve.ca>; from tom@uniserve.com on Fri, Jul 13, 2001 at 09:21:47AM -0700 References: <20010713103238.T75539@bsd.havk.org> <Pine.BSF.4.10.10107130920330.47572-100000@athena.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 13, 2001 at 09:21:47AM -0700, Tom wrote: > On Fri, 13 Jul 2001, Steve Price wrote: >> Anyone have any suggestions for what the most probable causes of >> the following panic are? >> >> panic: NMI indicates hardware failure > > Typically, it is a memory problem. If you use ECC or parity memory, > and a memory error is detected (and unfixable with ECC), the memory > subsystem deliveres a NMI. The other sources for NMI on PC platforms are hardware debuggers and the power supply (early supplies would generate NMI on loss of line power). > Tom -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010713133522.B14772>