Date: Thu, 16 Jan 2003 11:48:12 -0900 (AKST) From: Mike Tibor <tibor@tibor.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Trevor Johnson <trevor@jpj.net>, Wilko Bulte <wkb@freebie.xs4all.nl>, Kris Kennaway <kris@obsecurity.org>, <alpha@FreeBSD.ORG>, <current@FreeBSD.ORG> Subject: Re: unexpected machine check on 5.0 alpha Message-ID: <20030116114223.L27084-100000@xena.mikey.net> In-Reply-To: <15910.50391.473362.53094@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030116114223.L27084-100000>