Date: Sat, 19 Feb 2000 21:45:17 -0700 From: Wes Peters <wes@softweyr.com> To: Chuck Robey <chuckr@picnic.mat.net> Cc: Bruce Gingery <bgingery@gtcs.com>, FreeBSD Hackers List <freebsd-hackers@freebsd.org> Subject: Re: Recommended addition to FAQ (Troubleshooting) Message-ID: <38AF715D.ED0DAB03@softweyr.com> References: <Pine.BSF.4.21.0002191356360.23833-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey wrote:
>
> On Fri, 18 Feb 2000, Bruce Gingery wrote:
>
> > So I'll leave it up to you. There should be info at least in
> > a FAQ somewhere that indicates that bad RAM is not something
> > that can be ruled out until tested adequately, and perhaps a
> > checklist of symptoms that (virtually) ALWAYS indicate bad RAM,
> > or at least should make it suspect.
>
> It's *precisely* that attitude that makes up all immediately and
> completely against recommending any memory tester whatsoever. You
> apparently didn't read what Jordan told you closely enough to catch the
> main point:
>
> There is *no possible software method* of catching memory errors, with
> more than a 25% chance of really catching errors!
Sure there is, and it's included in FreeBSD by default: make -j 8 world
;^)
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38AF715D.ED0DAB03>