From owner-freebsd-stable@FreeBSD.ORG  Thu Aug  8 14:20:05 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 720EED6F
 for <freebsd-stable@freebsd.org>; Thu,  8 Aug 2013 14:20:05 +0000 (UTC)
 (envelope-from eric@vangyzen.net)
Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com
 [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1A812263A
 for <freebsd-stable@freebsd.org>; Thu,  8 Aug 2013 14:20:04 +0000 (UTC)
X-Loopcount0: from 64.238.244.148
X-IronPort-AV: E=Sophos;i="4.89,839,1367989200"; d="scan'208,217";a="39384111"
Message-ID: <5203A90D.6020008@vangyzen.net>
Date: Thu, 8 Aug 2013 09:19:57 -0500
From: Eric van Gyzen <eric@vangyzen.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130702 Thunderbird/17.0.7
MIME-Version: 1.0
To: J David <j.david.lists@gmail.com>
Subject: Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1
References: <1375737316.96778.10.camel@firkin.mischler.com>
 <520116DE.8030305@vangyzen.net> <52013992.4050101@vangyzen.net>
 <CABXB=RRuEEVeNmyOXP4KabF=9Q31jzxoXMopi1LEqBTE6+540A@mail.gmail.com>
In-Reply-To: <CABXB=RRuEEVeNmyOXP4KabF=9Q31jzxoXMopi1LEqBTE6+540A@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-stable@freebsd.org, dave@mischler.com
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 14:20:05 -0000

On 08/06/2013 14:23, J David wrote:
> On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen <eric@vangyzen.net> wrote:
>>> on an otherwise idle amd64 system with 4 CPUs.  The first command in the
>>> build.log file:
>>>
>>>     rm -rf /usr/obj/home/freebsd/tmp
>>>
>>> took over three minutes.  It should have taken about three /seconds/.
>>>
>>> "uptime" reported a load average of around 1.00.
>>> "top" showed no threads (user or kernel) using CPU.
>>> "iostat" showed an average of less than 20 tps on ada0.
>>> "rm" was usually in the RUN state.
> We are looking at something similar.  Would you be able to try to
> reproduce it using a kernel with:
>
> nooptions	SCHED_ULE
> options		SCHED_4BSD
>
> to see if it makes a difference?  It seems to, but the problem is
> inconsistent enough that I can't be sure.

The 4BSD scheduler does //not// exhibit this problem.  I tested with the
latest releng/9.2 (r254054) and an otherwise GENERIC config.

Eric