Date: Mon, 24 Jun 1996 10:00:26 -0700 From: Ernest Hua <hua@chromatic.com> To: Don Yuniskis <dgy@rtd.com> Cc: jsigmon@www.hsc.wvu.edu (Jeremy Sigmon), hackers@freebsd.org, hua@xenon.chromatic.com Subject: Re: Memory tests ... Message-ID: <199606241700.KAA16970@server1.chromatic.com> In-Reply-To: Your message of "Mon, 24 Jun 1996 06:23:01 PDT." <199606241323.GAA29600@seagull.rtd.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > According to the systems people around here, the best way to test memory is > > to put it into a Novell server. If the memory is flakey it will let > > you know fast. (ABEND???) > > I thinks someone around here has a 4.1 2 user box setup just for that > > purpose. > > Are people looking for *exhaustive* tests, "quick and dirty" tests, > diagnostic tests, or what? There are different solutions for each > of these. But I think just the "make world" style tests add very little > value (tho' prehaps, they are probably easiest to invoke...) I would prefer a thorough set of tests such as some reasonably optimized 1's and 0's test. I'm not familiar with algorithms for testing "flaky" versus "stuck". Ern
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606241700.KAA16970>