From owner-freebsd-current@FreeBSD.ORG  Mon Jul 25 16:23:24 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 79767106566C;
	Mon, 25 Jul 2011 16:23:24 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.95.76.21])
	by mx1.freebsd.org (Postfix) with ESMTP id 56DEA8FC1A;
	Mon, 25 Jul 2011 16:23:24 +0000 (UTC)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
	[127.0.0.1])
	by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id
	p6PGNNRo027433; Mon, 25 Jul 2011 09:23:23 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id
	p6PGNNdE027432; Mon, 25 Jul 2011 09:23:23 -0700 (PDT)
	(envelope-from sgk)
Date: Mon, 25 Jul 2011 09:23:23 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Andriy Gapon <avg@FreeBSD.org>
Message-ID: <20110725162323.GA27425@troutmask.apl.washington.edu>
References: <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> <4E2D3EBB.9060508@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E2D3EBB.9060508@FreeBSD.org>
User-Agent: Mutt/1.4.2.3i
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 16:23:24 -0000

On Mon, Jul 25, 2011 at 01:00:27PM +0300, Andriy Gapon wrote:
> 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.
> 

I won't have time until next week to investigate.

-- 
Steve