From owner-freebsd-hackers@freebsd.org Wed Mar 8 18:05:58 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 1188ED037BF for ; Wed, 8 Mar 2017 18:05:58 +0000 (UTC) (envelope-from stesin@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB5BAFAA for ; Wed, 8 Mar 2017 18:05:57 +0000 (UTC) (envelope-from stesin@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id m27so44948438iti.1 for ; Wed, 08 Mar 2017 10:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4ar6Sx9x3t554nbs81zrUu96b1TBuvOQSkxQUxXBQ9Q=; b=JvyWpUCnDHZZlaCP1GlIOYu6Gh/TyjOrUuGHOz/AULoWACsfJnO5vt+IwN1sJcjEjA DOI8fljt27PDS1OOwIt1UNF2vhJ1rxAT/uwt5R5BrVSx5+DKbMyKzs+YNH+O35m/GS+I Rwg9oZKEnAzo9UkXaoK48u5uP5/pR7sw+CnhMMVSlt947p7patdhgjv6kE/NUdevNh0V XqcmpUUQfohP3qLORC2AuZb/LjQufEJ/3Dsw1du3kxUDy1wBRDUil8D2jDq078Zt+K/e UAi5j6+L/muLSCufSbtE7F2ib+EVw33cR7pvzShGP1LXJl79bbtfacxvOwoyFfyATQmj sB4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4ar6Sx9x3t554nbs81zrUu96b1TBuvOQSkxQUxXBQ9Q=; b=VXY3/Q2InOdqui/nFOpWjaYIb4y4rFnUiGcefLbxpC7MdzUdLYWBtoI9JcLIJcXbvm 69kkEHahNUm9LVSkWu0w3y+1p2qbuvme6y86bsLF2EesMqWpbK+VCptNyJv05MTuS6ED yTVNInsNOfuEYMraL6Mqj4j4Hp6zNe2d4CU+wleps8SsVzRZqvkGrvlrcoGtACLi/i+c ZHj2l6rFVGRNS/I/kkiJLsVRRWHA8PajJ4XEK3fLDhV7Eu45XTvEp1kdQ2bAX9pQoRXL 2fZiMR6HW624nAdVxBZZ0gy5rY7euvXeXOxLnovJDzgEyKsrMwxr4Pi1t3eDhDGCdrjU S+Cg== X-Gm-Message-State: AMke39lR2DV+AYz/8jICwzBJwIMpjJNoly5WMjvDO2nAkvolYSEzCKa/+K2F7fmOIUO8+gIrF5fIwLJEdPU52w== X-Received: by 10.107.167.204 with SMTP id q195mr8540525ioe.170.1488996357134; Wed, 08 Mar 2017 10:05:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.5.195 with HTTP; Wed, 8 Mar 2017 10:05:55 -0800 (PST) Received: by 10.36.5.195 with HTTP; Wed, 8 Mar 2017 10:05:55 -0800 (PST) In-Reply-To: <201703081727.v28HRvp6001740@pdx.rh.CN85.dnsmgr.net> References: <86b89c6c-9a00-1033-4181-a7e0da2ed66f@digitaldaemon.com> <201703081727.v28HRvp6001740@pdx.rh.CN85.dnsmgr.net> From: Andrii Stesin Date: Wed, 8 Mar 2017 20:05:55 +0200 Message-ID: Subject: Re: Help with silent reboot of 10.3-stable system To: "Rodney W. Grimes" Cc: hackers list , Jan Knepper Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.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, 08 Mar 2017 18:05:58 -0000 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" >