From owner-freebsd-current Thu Jan 16 12:56:29 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 60F1E37B401; Thu, 16 Jan 2003 12:56:27 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6527143F13; Thu, 16 Jan 2003 12:56:26 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.6/8.12.6) with ESMTP id h0GKuFro009595 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Jan 2003 15:56:15 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h0GKuAw77782; Thu, 16 Jan 2003 15:56:10 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15911.7274.187485.449582@grasshopper.cs.duke.edu> Date: Thu, 16 Jan 2003 15:56:10 -0500 (EST) To: Mike Tibor Cc: Trevor Johnson , Wilko Bulte , Kris Kennaway , , Subject: Re: unexpected machine check on 5.0 alpha In-Reply-To: <20030116114223.L27084-100000@xena.mikey.net> References: <15910.50391.473362.53094@grasshopper.cs.duke.edu> <20030116114223.L27084-100000@xena.mikey.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 Mike Tibor writes: > 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 That's nice. If you'd care to see the console logs from a "new" type of machine I've been bringing up (multi-hose AS2100A) which crashes with 660s when I read from a bad IO address, I'd be more than happy to share... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message