From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 1 00:29:21 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31EFF106564A for ; Wed, 1 Aug 2012 00:29:21 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 0472E8FC14 for ; Wed, 1 Aug 2012 00:29:20 +0000 (UTC) Received: from JRE-MBP-2.local (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q710TDWF081067 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 31 Jul 2012 17:29:13 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <50187853.7080206@freebsd.org> Date: Tue, 31 Jul 2012 17:29:07 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Yuri References: <501871FD.601@rawbw.com> In-Reply-To: <501871FD.601@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to diagnose system freezes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2012 00:29:21 -0000 On 7/31/12 5:02 PM, Yuri wrote: > One of my 9.1-BETA1 systems periodically freezes. If sound was > playing, it would usually cycle with a very short period. And system > stops being sensitive to keyboard/mouse. Also ping of this system > doesn't get a response. > I would normally think that this is the faulty memory. But memory > was recently replaced and tested with memtest+ for hours both before > and after freezes and it passes all tests. > One out of the ordinary thing that is running on this system is > nvidia driver. But the freezes happen even when there is no graphics > activity. > Another out of the ordinary thing is that the kernel is built for > DTrace. But DTrace was never used in the sessions that had a freeze. > > What is the way to diagnose this problem? The answer depends on a number of things but an NMI can be useful if you have some way of generating them. (some IPMI implementations can allw you to generate them and some motherboards have jumpers to allow you to attach a 'nmi-button'. The fact that ping is not responsive is important, as that is done at a very low level but it may still be alive down there somewhere. Make sure you have debugging enabled in your kernel. That will catch quite a few 'hangs'. as also mentioned by others... a serial console and DDB may also be useful in some hangs. Julian > CPU: i7 CPU 920 @ 2.67GHz > Memory: 24GB > MB: P2T > > Yuri > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > >