Date: Tue, 26 Feb 2002 23:01:41 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: yvictorovich@optima-hyper.com, alpha@FreeBSD.ORG Subject: Re: "unexpected machine check" on AS1000A Message-ID: <20020226230141.A76553@freebie.xs4all.nl> In-Reply-To: <15483.65041.7582.593390@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Feb 26, 2002 at 04:28:49PM -0500 References: <E052D8D86575D511A0E1009027D3B86218B4F8@hqsmail.SNET> <E052D8D86575D511A0E1009027D3B86215088A@hqsmail.SNET> <15483.65041.7582.593390@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 26, 2002 at 04:28:49PM -0500, Andrew Gallatin wrote: > > Yuri Victorovich writes: > > Nope, seems that reseating, cleaning, rotating SIMMs doesn't help. > > Is it a way to find which SIMM exactly causes the problem? By those > > values that it loggs on "unexpected machine check" crash? > > > > Yes & we could also log more information for the correctable errors > too. However, doing this requires having sufficient documentation, > which I don't think we do. Yep, I think exactly that information is CPQ confidential. T64 has a binary errorlogger that uses this kind of thing. Along with DECevent & CPQanalyse one can really analyse a lot of nitty gritty problems. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020226230141.A76553>