From owner-freebsd-stable Fri Jul 13 13:35:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id B78ED37B401 for ; Fri, 13 Jul 2001 13:35:35 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id NAA15290; Fri, 13 Jul 2001 13:35:22 -0700 (MST) (envelope-from chad) Date: Fri, 13 Jul 2001 13:35:22 -0700 From: "Chad R. Larson" To: Tom Cc: Steve Price , stable@FreeBSD.ORG Subject: Re: NMI panics Message-ID: <20010713133522.B14772@freeway.dcfinc.com> References: <20010713103238.T75539@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from tom@uniserve.com on Fri, Jul 13, 2001 at 09:21:47AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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