From owner-freebsd-questions@freebsd.org Fri Jun 2 16:48:19 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 7F909BFB285 for ; Fri, 2 Jun 2017 16:48:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 4181B6A905 for ; Fri, 2 Jun 2017 16:48:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x22a.google.com with SMTP id s3so8200460oia.0 for ; Fri, 02 Jun 2017 09:48:19 -0700 (PDT) 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=xlzKj3MAybW5ZSYqMhfgR9YJY63LFKPfYEik2iX5oXg=; b=ey0KwWLRhJDrrDh1XIynCBE2QgYyncOEYKyH2R14jFGpyPo6it33adCwM27ag3g2Ow 6vNvolFS1ZYC7YNH4ZcPSWSH5I+7zmXxBVTcrgHeFPNpkzEs734yqPmphnZETYE0QJuK f05udVBZFPVVuVRaLE/ZomzdreKY3Gf8keFSuxwx7j8hN6Vmn6DeJ+Cf+RDR5eaiLeoP 66l4FL0KBMVY3QHFN3QSvRTr1B3SBB960GHwWQrojrqes+8hFfAwCl8UVtHXMZ4//YR6 Z1X0SmXS1lcTVFZNKRj5sO3EpwWiFoxvD9C05VdcoD8swC0CbmSrooaf0Vu0xdct02oz 8l/w== 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=xlzKj3MAybW5ZSYqMhfgR9YJY63LFKPfYEik2iX5oXg=; b=SQK60NhaQWRUsNDx17qNvpxtxtPms2rU1rN34dq1h8XcVuil7E6KqKJS2D6kEiM72Y 01IWJz0O7ynr88lXjCRKsenwWGwtIzKWz1Izvh4q0JK0flxlwFqnCMupj9MuO+S+YTFq AjwpgJE7Nz5eBGT+N9t0G67M2uHAa915u9OtJK5xif4VSswn/9Ur2hCE83BIjMtAkB4T R9larqYttX0zNAvK60i4L2x7UdPefzKXA/EXI8rfHcLSTzZy2Pw5itKtk2A6Hg4DElZb wlSkz8j8TPgZZRDqUcWKW9Yvk6fOU7kLLdPZ58AM16+l+aX+/N1nU97KRvxqV7w6Kxdm 0q5g== X-Gm-Message-State: AKS2vOzAPAAq+Al2Uvkmr/xfQtOOAGWVzJ5eUliigiNzx/PPfOXk20fu TFD0MAu6p6+KtAGv5/27GoPXNiuJ3DhT X-Received: by 10.157.39.14 with SMTP id r14mr5445441ota.11.1496422098358; Fri, 02 Jun 2017 09:48:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.29.69 with HTTP; Fri, 2 Jun 2017 09:48:17 -0700 (PDT) In-Reply-To: <20170601235447.C98304@sola.nimnet.asn.au> References: <20170601235447.C98304@sola.nimnet.asn.au> From: Mehmet Erol Sanliturk Date: Fri, 2 Jun 2017 09:48:17 -0700 Message-ID: Subject: Re: Advice on kernel panics To: Ian Smith Cc: Raimo Niskanen , FreeBSD Questions Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Fri, 02 Jun 2017 16:48:19 -0000 On Thu, Jun 1, 2017 at 7:34 AM, Ian Smith wrote: > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > On Thu, 1 Jun 2017 10:27:49 +0200 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. > > 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. > > 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. > > cheers, Ian > _______________________________________________ > > "Panics about every three days" may suggest another software problem : With respect to your executed programs , system resources , especially memory or OS data structures , may be allocated , but not freed properly without any warning message ( or message may be missed ) . When OS requires to do a process , but there is no a sufficient resource , a panic may be triggered ( without background reasons ) . To isolate this possibility , if ever is possible to find the panic point ( in the sense of a routine in a source file ) , it may show an important clue to proceed a more fruitful way to solve the problem . Mehmet Erol Sanliturk