From owner-freebsd-questions@freebsd.org Sat Aug 13 00:27:41 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 076E5BB7BAE for ; Sat, 13 Aug 2016 00:27:41 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.he.net", Issuer "GeoTrust SSL CA - G4" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ECE3D1BA7 for ; Sat, 13 Aug 2016 00:27:40 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from ::ffff:99.100.19.101 ([99.100.19.101]) by holgerdanske.com for ; Fri, 12 Aug 2016 17:20:54 -0700 Subject: Re: Monitoring server for crashes To: freebsd-questions@freebsd.org 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> From: David Christensen X-Enigmail-Draft-Status: N1110 Message-ID: Date: Fri, 12 Aug 2016 17:20:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0 MIME-Version: 1.0 In-Reply-To: <11590.128.135.52.6.1471018231.squirrel@cosmo.uchicago.edu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Aug 2016 00:27:41 -0000 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