From owner-freebsd-alpha Tue Feb 26 14: 2:19 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 043F337B487 for ; Tue, 26 Feb 2002 14:01:48 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g1QM1f176582; Tue, 26 Feb 2002 23:01:41 +0100 (CET) (envelope-from wkb) Date: Tue, 26 Feb 2002 23:01:41 +0100 From: Wilko Bulte To: Andrew Gallatin Cc: yvictorovich@optima-hyper.com, alpha@FreeBSD.ORG Subject: Re: "unexpected machine check" on AS1000A Message-ID: <20020226230141.A76553@freebie.xs4all.nl> References: <15483.65041.7582.593390@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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