From owner-freebsd-questions@freebsd.org Thu Jun 1 05:10:39 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 72200AF89A8 for ; Thu, 1 Jun 2017 05:10:39 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5366284C8A for ; Thu, 1 Jun 2017 05:10:39 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 5A34F11022A for ; Thu, 1 Jun 2017 00:10:31 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 34561110229; Thu, 1 Jun 2017 00:10:31 -0500 (CDT) Date: Thu, 1 Jun 2017 00:10:30 -0500 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: Advice on kernel panics Message-ID: <20170601051030.GA39861@geeks.org> References: <20170529092043.GA89682@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170529092043.GA89682@erix.ericsson.se> User-Agent: Mutt/1.8.2 (2017-04-18) X-Virus-Scanned: ClamAV using ClamSMTP 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: Thu, 01 Jun 2017 05:10:39 -0000 On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > I have a server that panics about every 3 days and need some advice on how > to handle that. I'd expect it is some sort of hardware failure, as I would expect kernel panics more on the order of once a decade with FreeBSD. Ie. I've seen one or two on my hundred or so servers, but its pretty rare. Check and recheck your hardware items. Runup memtest86+. Check your drive hardware, turn on SMART checking.