Date: Tue, 28 Aug 2001 00:40:59 -0400 (EDT) From: "Brandon D. Valentine" <bandix@looksharp.net> To: David Kelly <dkelly@grumpy.dyndns.org> Cc: Tenebrae <tenebrae@niceboots.com>, Alex Varju <varju@webct.com>, <freebsd-stable@FreeBSD.ORG> Subject: Re: 4.4-rc instability Message-ID: <20010828003737.M85068-100000@turtle.looksharp.net> In-Reply-To: <200108280434.f7S4YZw91567@grumpy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Aug 2001, David Kelly wrote: >Used to run an installation of about 40 machines, mixed SGI and Sun. >Part of my weekly check was a scan for logged recovered memory errors. >They simply happened sometimes to even healthy machines. But often when >a machine started crashing or unusual process termination, I'd find >several memory errors logged. When the machine is under a maintenance >contract entries in the system log make it easy to have the soft memory >replaced before the machine becomes unstable. I'll chime in with support for buying quality ECC memory. I admin what is quickly reaching fifty SGIs and there is nothing better than having a machine tell you when it's memory is going bad. PCs need something like SGI's ARCS PROM diagnostic tools. -- "Never put off until tomorrow what you can do today. There might be a law against it by that time." -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine <bandix at looksharp.net> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010828003737.M85068-100000>