Date: Thu, 16 Jan 2003 21:54:38 +0100 From: Bernd Walter <ticso@cicely8.cicely.de> To: Mike Tibor <tibor@tibor.org> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, 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: <20030116205438.GA62457@cicely8.cicely.de> In-Reply-To: <20030116114223.L27084-100000@xena.mikey.net> References: <15910.50391.473362.53094@grasshopper.cs.duke.edu> <20030116114223.L27084-100000@xena.mikey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 16, 2003 at 11:48:12AM -0900, Mike Tibor wrote: > 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: Single bit errors on ram are non fatal and reported by FreeBSD as processor correctable error. In the most cases you don't get fatal memory errors without some non-fatal errors. You may want to remove and reinsert the simms. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de 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?20030116205438.GA62457>