From owner-freebsd-questions@FreeBSD.ORG Wed Dec 5 05:19:56 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85B6416A418 for ; Wed, 5 Dec 2007 05:19:56 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 47E5613C459 for ; Wed, 5 Dec 2007 05:19:56 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <475634F5.6030901@intersonic.se> Date: Wed, 05 Dec 2007 06:19:49 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20071103) MIME-Version: 1.0 To: yar References: <14164268.post@talk.nabble.com> In-Reply-To: <14164268.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: What is best method to debug freezes/hangs? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2007 05:19:56 -0000 yar wrote: > My question is how best to go about debugging sporadic freezes and hangs. > Just looking for general methods. On a couple of our IDS systems there > are sporadic hangs or freezes that occur every couple weeks or so, that are > recoverable by either system reboots or taking out and reinserting the Gig > fiber ethernet sniffing cables, but I never can find anything in > /var/logs/messages to tell what is going on. I'm assuming that may have to > compile in kernel debugger support, but from what I read briefly, doesn't > that require an actual crash with the resultant reboot and a debugger > readable file left in /var/crash? That doesn't happen, there is no > automatic reboot just a freeze/hang (box falls off network and at the > console unable to type until one of the two above mentioned measures are > take. In my case with the above behaviour a debug kernel and ctrl+alt+esc would work and that is probably true most of the times. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html HTH, --per