Date: Fri, 12 Aug 2016 17:20:54 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: freebsd-questions@freebsd.org Subject: Re: Monitoring server for crashes Message-ID: <f27d9894-ebae-5b52-4a98-8d9c812559bf@holgerdanske.com> In-Reply-To: <11590.128.135.52.6.1471018231.squirrel@cosmo.uchicago.edu> References: <57ADDA5F.4000405@webtent.org> <61294.128.135.52.6.1471013465.squirrel@cosmo.uchicago.edu> <57ADF096.8010608@webtent.org> <11590.128.135.52.6.1471018231.squirrel@cosmo.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/12/2016 09:10 AM, Valeri Galtsev wrote:
>
> On Fri, August 12, 2016 10:51 am, Robert Fitzpatrick wrote:
>> Valeri Galtsev wrote:
>>> ... Run memtest96 at this point for at least 48 hours (or at the very
>>> minimum 2-3 full loops of test).
I use memtest86+:
http://www.memtest.org/
> 1. re-seat all RAM modules.
I would advise testing before changing anything. The strategy is:
devise a reproducible test that invokes the bug, use the test to isolate
the bug, fix the bug, re-run test to verify the bug is fixed, re-run the
test periodically to verify that that bug has not returned.
Also -- buy a power supply tester and use it.
David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f27d9894-ebae-5b52-4a98-8d9c812559bf>