From owner-freebsd-questions@freebsd.org Sun Mar 19 16:05:05 2017 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 95939D13261 for ; Sun, 19 Mar 2017 16:05:05 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C24FD0E for ; Sun, 19 Mar 2017 16:05:04 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v2JG4eTa022796; Mon, 20 Mar 2017 03:04:41 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 20 Mar 2017 03:04:40 +1100 (EST) From: Ian Smith To: Bertram Scharpf cc: CeDeROM , freebsd-questions@freebsd.org Subject: Re: Second severe crash in six weeks In-Reply-To: Message-ID: <20170319235808.F10005@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Mar 2017 16:05:05 -0000 In freebsd-questions Digest, Vol 667, Issue 9, Message: 7 On Sun, 19 Mar 2017 12:46:52 +0100 Bertram Scharpf wrote: > On Friday, 17. Mar 2017, 22:58:32 +0100, CeDeROM wrote: > > Bertam, are you sure you are working on a clean filesystem? Did you > > run FSCK -F / from single user as suggested?? > > Didn't help. Bertram, everything about your various issues suggests hardware to me. Memory is usually the first thing to check, but all sorts of components can go flaky, sometimes in almost non-deterministic (ie, weird) ways. Have you tried the suggested memtest86 test, for at least an hour or so? Another useful tester is sysutils/stress, which may be installed and run without rebooting or other inconvenience. Something like: # stress -c 2 -t 1200 & will run 2 CPUs at 100% for 20 minutes in background; adjust to >= cpu count. Meanwhile keep an eye on system temperatures and fans; this gets CPU/s as hot as they can. Your system should be engineered to cope with running at full rated load, with some headroom. cheers, Ian