From owner-freebsd-stable Fri Jul 13 8:46:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 4070737B401 for ; Fri, 13 Jul 2001 08:46:14 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id D371C3E31; Fri, 13 Jul 2001 08:46:13 -0700 (PDT) To: Steve Price Cc: stable@freebsd.org Subject: Re: NMI panics In-Reply-To: <20010713103238.T75539@bsd.havk.org>; from steve@havk.org on "Fri, 13 Jul 2001 10:32:38 -0500" Date: Fri, 13 Jul 2001 08:46:13 -0700 From: Dima Dorfman Message-Id: <20010713154613.D371C3E31@bazooka.unixfreak.org> 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 Steve Price writes: > Anyone have any suggestions for what the most probable causes of > the following panic are? > > panic: NMI indicates hardware failure It's obvious that something is generating an NMI when it shouldn't. There's a sysctl, machdep.panic_on_nmi, that controls whether that should result in a panic or not. You might want to set it to 0 and see if the machine goes haywire or not. Perhaps it'd be nice to know if the NMI was delivered if !panic_on_nmi, but that's not currently implemented. > > Thanks. > > -steve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message