Date: Thu, 16 Jan 2003 09:42:31 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Mike Tibor <tibor@tibor.org> 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: <15910.50391.473362.53094@grasshopper.cs.duke.edu> In-Reply-To: <20030116005541.L26353-100000@xena.mikey.net> References: <20030116033841.N30783-100000@blues.jpj.net> <20030116005541.L26353-100000@xena.mikey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tibor writes: > On Thu, 16 Jan 2003, Trevor Johnson wrote: > > > I just got a similar crash: > > > > unexpected machine check: > > > > mces = 0x1 > > vector = 0x670 > 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. Drew 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?15910.50391.473362.53094>