From owner-freebsd-current@FreeBSD.ORG  Mon Jul 25 10:00:35 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7180C1065670
	for <freebsd-current@FreeBSD.org>; Mon, 25 Jul 2011 10:00:35 +0000 (UTC)
	(envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id BA6C88FC13
	for <freebsd-current@FreeBSD.org>; Mon, 25 Jul 2011 10:00:34 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA13998;
	Mon, 25 Jul 2011 13:00:29 +0300 (EEST)
	(envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
	by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1QlHxd-000GfE-7N; Mon, 25 Jul 2011 13:00:29 +0300
Message-ID: <4E2D3EBB.9060508@FreeBSD.org>
Date: Mon, 25 Jul 2011 13:00:27 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
References: <20110706170132.GA68775@troutmask.apl.washington.edu>
	<5080.1309971941@critter.freebsd.dk>
	<20110706180001.GA69157@troutmask.apl.washington.edu>
	<4E14A54A.4050106@freebsd.org> <4E155FF9.5090905@FreeBSD.org>
	<20110707151440.GA75537@troutmask.apl.washington.edu>
	<4E160C2F.8020001@FreeBSD.org>
	<20110707200845.GA77049@troutmask.apl.washington.edu>
	<ivf221$oo2$1@dough.gmane.org> <4E1B1198.6090308@FreeBSD.org>
	<20110711161654.GA97361@troutmask.apl.washington.edu>
	<4E1C003B.4090604@FreeBSD.org>
In-Reply-To: <4E1C003B.4090604@FreeBSD.org>
X-Enigmail-Version: 1.2pre
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org
Subject: Re: Heavy I/O blocks FreeBSD box for several seconds
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: Mon, 25 Jul 2011 10:00:35 -0000

on 12/07/2011 11:05 Andriy Gapon said the following:
> I think that the best thing you can further provide (as objective evidence for
> the problem at hand) is ktr(4) traces for at least KTR_SCHED mask.  Perhaps you
> even already have them from your previous sessions with Jeff.
> 
> P.S. This is not a promise to actually debug this issue based on the traces :-)

So do you have an opportunity to provide this kind of information?
Actually I would like KTR_SCHED|KTR_INTR|KTR_PROC|KTR_SYSC mask.
Also, sysctl kern.sched output would be useful too.
This is for the ULE case, of course.

-- 
Andriy Gapon