From owner-freebsd-current@FreeBSD.ORG  Wed Oct 12 17:24:12 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 032071065675;
	Wed, 12 Oct 2011 17:24:12 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
	by mx1.freebsd.org (Postfix) with ESMTP id BA9558FC0A;
	Wed, 12 Oct 2011 17:24:11 +0000 (UTC)
Received: from ds4.des.no (des.no [84.49.246.2])
	by smtp.des.no (Postfix) with ESMTP id C3B9B1FFC33;
	Wed, 12 Oct 2011 17:24:10 +0000 (UTC)
Received: by ds4.des.no (Postfix, from userid 1001)
	id B64E0B95F; Wed, 12 Oct 2011 19:24:10 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Alexander Motin <mav@FreeBSD.org>
References: <86bou59gpf.fsf@ds4.des.no> <4E83186C.4080707@FreeBSD.org>
Date: Wed, 12 Oct 2011 19:24:10 +0200
In-Reply-To: <4E83186C.4080707@FreeBSD.org> (Alexander Motin's message of
	"Wed, 28 Sep 2011 15:51:56 +0300")
Message-ID: <86botmjf7p.fsf@ds4.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: current@freebsd.org
Subject: Re: 9 hangs with idletick = 0
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Oct 2011 17:24:12 -0000

Alexander Motin <mav@FreeBSD.org> writes:
> If short freezes you've descrived happens often enough, you may try to
> log them down with enabling KTR_SPARE2 ktr event type and disabling
> logging within few seconds after such freeze happened.

I've been working with adri to try to isolate it.  We've eliminated nfs
and zfs as possible sources.  I definitely think it's network-related,
because I can trigger it by downloading a large file to /dev/null.

Interestingly, it looks like serial console activity wakes it up - not
immediately, but when I hooked up the console, it woke up within seconds
after being frozen for almost ten minutes.

I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
and KTR_SCHED enabled by default.  I'll see what turns up.  I'm also
going to try machdep.idle=3Dhlt with kern.eventtimer.idletick=3D0, and using
a PCI re(4) instead of the on-board msk(4) while running with default
settings.

BTW, can I suggest appropriating one of KTR_SPARE[234] and renaming it
to KTR_CLOCK?  I don't see why cxgb should use them, let alone all
three; it should use KTR_DEV or KTR_NET instead.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no