Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Jul 2000 08:24:13 +0200
From:      Wilko Bulte <wkb@freebie.demon.nl>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        Alec Wolman <wolman@cs.washington.edu>, freebsd-alpha@freebsd.org
Subject:   Re: warning: received processor correctable error message
Message-ID:  <20000713082413.B4271@freebie.demon.nl>
In-Reply-To: <14701.10036.523075.203941@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jul 12, 2000 at 10:21:53PM -0400
References:  <gallatin@cs.duke.edu> <14701.9102.36017.419004@grasshopper.cs.duke.edu> <200007130212.TAA25730@miles.cs.washington.edu> <14701.10036.523075.203941@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 12, 2000 at 10:21:53PM -0400, Andrew Gallatin wrote:
> 
> Alec Wolman writes:
>  > 
>  > If it is a memory error, will there be any way to detect which SIMM?
> 
> I don't know.  

Yes there is. But not with FreeBSD AFAIK. DECevent used on the binary errlog
of Tru64 UNIX gives you enough info, when combined with the service manuals
of a machine, to determine which DIMM/SIMM is problematic.

-- 
Wilko Bulte  	 	http://www.freebsd.org  "Do, or do not. There is no try"
wilko@freebsd.org	http://www.nlfug.nl	Yoda - The Empire Strikes Back


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?20000713082413.B4271>