From owner-freebsd-current@FreeBSD.ORG  Mon Oct 13 12:28:04 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 100CD16A4B3
	for <current@freebsd.org>; Mon, 13 Oct 2003 12:28:04 -0700 (PDT)
Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 06BEB43FA3
	for <current@freebsd.org>; Mon, 13 Oct 2003 12:28:03 -0700 (PDT)
	(envelope-from jroberson@chesapeake.net)
Received: from localhost (jroberson@localhost)
	by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h9DJRtA32685;
	Mon, 13 Oct 2003 15:27:55 -0400 (EDT)
	(envelope-from jroberson@chesapeake.net)
Date: Mon, 13 Oct 2003 15:27:55 -0400 (EDT)
From: Jeff Roberson <jroberson@chesapeake.net>
To: Arjan van Leeuwen <avleeuwen@piwebs.com>
In-Reply-To: <200310132119.57735.avleeuwen@piwebs.com>
Message-ID: <20031013152650.N56213-100000@mail.chesapeake.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: ULE status;
	interactivity fixed?  nice uninvestigated, HTT broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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, 13 Oct 2003 19:28:04 -0000

On Mon, 13 Oct 2003, Arjan van Leeuwen wrote:

> On Sunday 12 October 2003 23:21, Jeff Roberson wrote:
> > I commited a fix that would have caused all of the jerky behaviors under
> > some load.  I was not able to reproduce this problem with kde running
> > afterwards.
>
> Thanks for the fix! However, the problem is still here for me (using rev.
> 1.58). I just noticed it when compiling Mozilla. I can also still see it when
> logging out of GNOME.

Is it somewhat better?  I specifically fixed the problem for Giant but
other locks could have the same issues.  I suspect that they are far less
frequently held without Giant, but I could be wrong.

>
> Arjan
>