From owner-freebsd-hackers Fri Jan 29 06:53:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23351 for freebsd-hackers-outgoing; Fri, 29 Jan 1999 06:53:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from world.local (jcsbs.lanobis.de [62.104.165.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23342 for ; Fri, 29 Jan 1999 06:53:00 -0800 (PST) (envelope-from prumpf@jcsbs.lanobis.de) Received: from insula.local (insula [10.1.31.6]) by world.local (8.8.8/8.8.8) with ESMTP id PAA18607; Fri, 29 Jan 1999 15:50:27 +0100 Received: (from prumpf@localhost) by insula.local (8.8.8/8.8.8) id OAA21820; Fri, 29 Jan 1999 14:53:00 GMT Message-ID: <19990129145259.21967@insula.local> Date: Fri, 29 Jan 1999 14:52:59 +0000 From: Philipp Rumpf To: paul@originative.co.uk, hackers@FreeBSD.ORG Subject: Re: NMI failure address Reply-To: Philipp Rumpf References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from paul@originative.co.uk on Fri, Jan 29, 1999 at 12:21:00PM -0000 X-Accept-Language: en,de,se Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 29, 1999 at 12:21:00PM -0000, paul@originative.co.uk wrote: > Is there any way to find out which address is causing the NMI so you can > work out which DIMM has failed? You could disassemble the faulting instruction. If it is available, machine check architecture might help too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message