From owner-freebsd-current Thu Jan 16 12:48:19 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 643AF37B401; Thu, 16 Jan 2003 12:48:18 -0800 (PST) Received: from tibor.org (117-5-237-24-cable.anchorageak.net [24.237.5.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC2843F6B; Thu, 16 Jan 2003 12:48:17 -0800 (PST) (envelope-from tibor@tibor.org) Received: from xena.mikey.net (xena.mikey.net [192.168.1.2]) by tibor.org (Postfix) with ESMTP id 8929EAA1D; Thu, 16 Jan 2003 11:48:12 -0900 (AKST) Date: Thu, 16 Jan 2003 11:48:12 -0900 (AKST) From: Mike Tibor X-X-Sender: tibor@xena.mikey.net To: Andrew Gallatin Cc: Trevor Johnson , Wilko Bulte , Kris Kennaway , , Subject: Re: unexpected machine check on 5.0 alpha In-Reply-To: <15910.50391.473362.53094@grasshopper.cs.duke.edu> Message-ID: <20030116114223.L27084-100000@xena.mikey.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 16 Jan 2003, Andrew Gallatin wrote: (I wrote: ) > > I believe a 670 machine check can also result from a read of a > > non-existent I/O space. I'm not a programmer, but could that be the > > problem here? > > No, that's a 660. (system machine check). > A 670 is much more likely to be bad ram, bad cache, bad CPU, etc. > Its not always overheating. Hmm... well, I got that from Jay Estabrook (works at DEC/Compaq/HP) via the axp-list@redhat.com. The archived message is here: http://www.lib.uaa.alaska.edu/axp-list/archive/1998-12/0491.html FWIW... Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message