From owner-freebsd-stable Fri Jul 13 9:21:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 2C5EC37B431 for ; Fri, 13 Jul 2001 09:21:49 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 15L5hL-000DvN-00; Fri, 13 Jul 2001 09:21:47 -0700 Date: Fri, 13 Jul 2001 09:21:47 -0700 (PDT) From: Tom X-Sender: tom@athena.uniserve.ca To: Steve Price Cc: stable@freebsd.org Subject: Re: NMI panics In-Reply-To: <20010713103238.T75539@bsd.havk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, 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. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message