From owner-freebsd-hackers@FreeBSD.ORG  Wed Aug  1 19:38:43 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 57B9A106566B
	for <freebsd-hackers@freebsd.org>; Wed,  1 Aug 2012 19:38:43 +0000 (UTC)
	(envelope-from yanegomi@gmail.com)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com
	[209.85.213.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 1391E8FC0A
	for <freebsd-hackers@freebsd.org>; Wed,  1 Aug 2012 19:38:42 +0000 (UTC)
Received: by yenl8 with SMTP id l8so9084581yen.13
	for <freebsd-hackers@freebsd.org>; Wed, 01 Aug 2012 12:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=zOOkBNR500PgofTcEONsCsZ+I1ZIwS2T3QhL8epM0d8=;
	b=A2Rs534+cYMOobu93NygTWnzkjbrenKpGBMVOdZ4S5OjyXkf1lUld4k8EtHq7oO/j8
	WhW8OLgf/DcHRbnuq0jPqpoTTUogxUTRVijG0g2j+4iUgA6asltpKeF/zu76nzAg1R0/
	WX4LWVyKtipSH+6qH9yHCP3pv8I+ND4RV+tiliUId+QCuwBjT4vTGpyfboNDRuOaPSOL
	r9oINxkl4zjELoGhvZVVxJqhPXrwJl1Ciyii7Zl9YWNVxLRoalZEM5WPTREi2Xl3bqx9
	pbcWeS8IUYH0jO0mNlDbyAnrrsWI+6lreCXJiQQ2+bAaGwvFxZ8AokiT2fU1rhwTI9WG
	lnag==
MIME-Version: 1.0
Received: by 10.60.24.7 with SMTP id q7mr30670519oef.54.1343849922311; Wed, 01
	Aug 2012 12:38:42 -0700 (PDT)
Received: by 10.76.84.7 with HTTP; Wed, 1 Aug 2012 12:38:42 -0700 (PDT)
In-Reply-To: <501871FD.601@rawbw.com>
References: <501871FD.601@rawbw.com>
Date: Wed, 1 Aug 2012 12:38:42 -0700
Message-ID: <CAGH67wSOKJFRvK=HUpK7YnceGKVyvZMugwq0NQAt0R9LmOu9XA@mail.gmail.com>
From: Garrett Cooper <yanegomi@gmail.com>
To: Yuri <yuri@rawbw.com>
Content-Type: text/plain; charset=ISO-8859-1
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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 19:38:43 -0000

On Tue, Jul 31, 2012 at 5:02 PM, Yuri <yuri@rawbw.com> 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?

    As an aside, where do you see things lockup (Xorg, Firefox, etc)?
Can you remain sshed into the box or not? What sound driver are you
using and how are you playing sound/video?
Thanks,
-Garrett