From owner-freebsd-questions@freebsd.org Thu Jun 1 14:57:55 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 1F5FFAFEB92 for ; Thu, 1 Jun 2017 14:57:55 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 9DC957D1EA for ; Thu, 1 Jun 2017 14:57:53 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb25-73a9f9a0000055fe-f8-59302b68dc53 Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 35.6F.22014.86B20395; Thu, 1 Jun 2017 16:57:45 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 16:53:19 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51ErIxH009008 for ; Thu, 1 Jun 2017 16:53:18 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51ErIx9009007 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 16:53:18 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 16:53:17 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601145317.GE2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170601235447.C98304@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20170601235447.C98304@sola.nimnet.asn.au> "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2K7n26mtkGkQesBbouXXzexODB6zPg0 nyWAMYrLJiU1J7MstUjfLoErY8+6xUwFk4Qrjv56xtrAeImvi5GTQ0LAROLX+xesXYxcHEIC Rxglfj5pZYFwNjBKdO2bDJVpY5LYMusXI4TzhFHi0MwLzBD9ORJvPx1l6mLk4GARUJGYesQA JMwmYCrR+PMMK4gtIqAs8e/aRbByYaCSFVvvMYLYvECr1z1+ygxh60t8XPEKrF5IoFRi7uNT 7BBxQYmTM5+wgNjMAjoSC3Z/YgNZxSwgLbH8HwdImFPAXOL4yRVgFzAArWo7JQRiioJs/Qo1 UFtiwpsDrBMYRWYhmTkLycxZCDMXMDKvYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAgM74Nb fqvuYLz8xvEQowAHoxIP70otg0gh1sSy4srcQ4wSHMxKIrxHNIFCvCmJlVWpRfnxRaU5qcWH GKU5WJTEeR33XYgQEkhPLEnNTk0tSC2CyTJxcEo1MNZfZZodnzq7JYC5xCnh5m3pMxP79B/6 POuYMWPZhi+5d/xuT9+Q+ca88MaSLzfOHLhrujjs+aR7R3L90vvr1hYazTjO7hMd8Vm+4VLv gZYT2Y6+25cd3rDm+T3z5DzOHVZRjROuHpfxyvn8cb+QnvF1g6i41THblme9eDTz/8OCULnv fu+Eq28psRRnJBpqMRcVJwIAze7y3GsCAAA= 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 14:57:55 -0000 On Fri, Jun 02, 2017 at 12:34:43AM +1000, Ian Smith wrote: > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen wrote: > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > 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. > > > > I have removed one of four memory capsules - panicked again. Will rotate > > through all of them... > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > > > I have run memtest86+ over night - no errors found. > > > > I have installed smartmontools - no errors found, short and long self tests > > on both disks run fine. zpool scrub repaired 0 errors and has no known data > > errors. > > Everyone's suggesting hardware problems, and it's certainly worthwhile > eliminating that possibility - but this could be a software/OS issue. > > If it were me and hardware all checks out, I'd try posting the original > report - plus other details about the box and setup that you've since > mentioned - to freebsd-stable@, or maybe freebsd-fs@ since those fstat > reports seem to point to possible FS/zfs issues? at a wild guess .. > > One other hardware tester you might try is sysutils/stress which can > pound CPU, I/O, VM, disk as hard and for as long as you like, without > having to bring the box down. I've used this lots to generate heavy > loads. Keep a close eye on system temperatures during longer tests. Worth a try. > > Ah, just before posting, I see your latest with dmesg. Just on a quick > scan, I wonder if these are a bad indication? Maybe just a side-issue, > but powerd might not work, so again heat might be something to watch: > > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. This I will definitely look into! > > cheers, Ian -- / Raimo Niskanen, Erlang/OTP, Ericsson AB