From owner-freebsd-questions@freebsd.org Thu Jun 1 13:44:25 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 95A52AFD3E6 for ; Thu, 1 Jun 2017 13:44:25 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 21E907A1A8 for ; Thu, 1 Jun 2017 13:44:24 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-5a49e9a000000d37-ab-59301a35a6f4 Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 67.0A.03383.53A10395; Thu, 1 Jun 2017 15:44:22 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 15:41:31 +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 v51DfS0c002632 for ; Thu, 1 Jun 2017 15:41:28 +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 v51DfSnM002631 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 15:41:28 +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 15:41:28 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601134128.GB2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyM2K7ma6ZlEGkQfsTHouXXzexODB6zPg0 nyWAMYrLJiU1J7MstUjfLoEr48Hm5SwFh0Urnr67zN7AuF+gi5GTQ0LARGJbx0SWLkYuDiGB I4wSBz+cZ4ZwNjBKrH5/mh3CaWOSuPzvIlTZE0aJjv132CD6cyTefjrKBGKzCKhIzHp3kxnE ZhMwlWj8eYYVxBYRUJb4d+0iWFwYqGbF1nuMIDYv0O6+NWtZIGx9iY8rXrFCLDjLKHH/9FKo hKDEyZlPwGxmAR2JBbs/AS3mALKlJZb/4wAJcwoESuy9uYAJJMwAtKvtlBCIKQqy9ivYBUIC 2hIT3hxgncAoMgvJzFlIZs5CmLmAkXkVo2hxanFxbrqRsV5qUWZycXF+nl5easkmRmCIH9zy W3cH4+rXjocYBTgYlXh4bQQNIoVYE8uKK3MPMUpwMCuJ8ApIAoV4UxIrq1KL8uOLSnNSiw8x SnOwKInzOuy7ECEkkJ5YkpqdmlqQWgSTZeLglGpg7Dhy23PBWb7V7iGPgx7MmtWTL8any7pc x8+ieV3ZidkSPrujhH571+jfPP/QN+E9Y3gV0xyfxSHFb4+fydL+eFN31ZaGxUFXZFWua37c lc4e//dzSAKv9p2uR6dd0r6uapDalX0mQkAs4nZ25v/gY/PzzzBv0P6a8WHjmco3O6Lfnsy3 nfKRU4mlOCPRUIu5qDgRAHNFQkJtAgAA 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 13:44:25 -0000 On Thu, Jun 01, 2017 at 03:07:36AM -0700, Mehmet Erol Sanliturk wrote: > On Thu, Jun 1, 2017 at 1:27 AM, Raimo Niskanen < > raimo+freebsd@erix.ericsson.se> 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. > > > > > > Any further hints on how to "Check your drive hardware"? > > > > > > Thank you for your advice. > > -- > > > > / Raimo Niskanen, Erlang/OTP, Ericsson AB > > _______________________________________________ > > f > > > > > > Also check cables , because , sometimes , some connector parts are not > transmitting data properly . I'll see if I can do that. > Another possibility may be a faulty executable binary because some bits may > be changed in place . > Another possibility may be power level ( Watts ) of power supply : Adding > some new hardware part(s) may exceed capacity of existing power supply : > When executed programs require more power , due to insufficient power level > , circuits may be corrupted . This is a standard Dell Power Edge R320 with two disks of four and no extras except for an extension board with two more Ethernet ports, so that is rather unlikely, but worth looking into. > > If it is possible , by removing connectors of existing HDDs and installing > a new OS on a spare disk may show possibility of modified binary existence > . I will try "freebsd-update IDS" and see if it finds a checksum error. > > If the new install is not panicking , then existing installed parts may > have defective parts . > If the new install is also panicking , then your hardware ( for example , > main board , circuits in main board > ) has some trouble points . > > > Mehmet Erol Sanliturk Thank you for your advice. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB