From owner-freebsd-hackers@freebsd.org Wed Mar 15 18:45:29 2017 Return-Path: Delivered-To: freebsd-hackers@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 CCACBD0EC70 for ; Wed, 15 Mar 2017 18:45:29 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A8EA98EF for ; Wed, 15 Mar 2017 18:45:29 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id v2FIjLNJ050504 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Mar 2017 13:45:21 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id v2FIjL36050503; Wed, 15 Mar 2017 13:45:21 -0500 (CDT) (envelope-from bob) Date: Wed, 15 Mar 2017 13:45:21 -0500 From: Bob Willcox To: Andrii Stesin Cc: "Rodney W. Grimes" , hackers list Subject: Re: Help with silent reboot of 10.3-stable system Message-ID: <20170315184521.GB8132@rancor.immure.com> Reply-To: Bob Willcox References: <86b89c6c-9a00-1033-4181-a7e0da2ed66f@digitaldaemon.com> <201703081727.v28HRvp6001740@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2017 18:45:29 -0000 Just to follow up on this. I updated the system to r314889 nearly a week ago and it hasn't rebooted since. No real idea if this had anything to do with it or not. The other thing that I did is order new hardware and start building a replacement system. Maybe that was it! :) Bob On Wed, Mar 08, 2017 at 08:05:55PM +0200, Andrii Stesin wrote: > I bet for faulty RAM module > > On Mar 8, 2017 19:47, "Rodney W. Grimes" > wrote: > > > > Is your system swapping to disk? Heavily? > > > > > > Might want to check the swap space on disk. > > > > > > I had spontaneous reboots some years ago because of bad swap space on > > > disk. (Got a new disk, 'dd'-ed the old disk to the new disk, reboot on > > > the new disk and everything was fine) > > > > > > Jan > > > > Good possibilty too, though usually this one causes console message > > to be spewed out and evetually a swap pager panic. Though no evidence > > is left behind beccase the disk couldnt be used to indicate an issue. > > > > Your probably not around the console when this happens Bob? > > It may be possible to hook up a serial console and capture > > the panic if it is happening. > > > > There are other failue modes that leave no on disk trace as well, > > but well spit out a panic to a serial console. > > > > > On 03/07/2017 20:56, Bob Willcox wrote: > > > > Over the past month or so my network fileserver system (NFS support > > for my > > > > entire, small, network) has begun silently rebooting itself. Here is > > the uname > > > > -a output: > > > > > > > > FreeBSD vader.immure.com 10.3-STABLE FreeBSD 10.3-STABLE #15 r313997: > > Mon Feb 20 14:40:00 CST 2017 bob@vader.immure.com:/usr/obj/usr/src/sys/GENERIC > > amd64 > > > > > > > > At first I suspected that it might be the power supply as it was a > > couple of > > > > years old so I replaced that. Unfortunately, it has begun doing it > > again (had > > > > a couple of weeks respite) so now my suspicions seem to have been > > incorrect. > > > > > > > > I was hoping that someone might be able to give me some clues on what > > I can do > > > > to reveal the problem. Are there any general debug settings for the > > kernel (or > > > > elsewhere) that would maybe give an indication of why it is being > > rebooted > > > > (assuming it's a software problem)? > > > > > > > > Thanks for any suggestions you may have! > > > > > > > > Bob > > > > > > > > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@ > > freebsd.org" > > > > > > > -- > > Rod Grimes > > rgrimes@freebsd.org > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Bob Willcox | If a program is useful, it will be changed. bob@immure.com | Austin, TX |