From owner-freebsd-stable@FreeBSD.ORG Wed Jan 30 14:23:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 724D616A55F for ; Wed, 30 Jan 2008 14:23:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6FAB313C4EE for ; Wed, 30 Jan 2008 14:23:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 06F941A4D82; Wed, 30 Jan 2008 06:23:00 -0800 (PST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 30 Jan 2008 08:55:14 -0500 User-Agent: KMail/1.9.7 References: <1199812249.96494.133.camel@predator-ii.buffyverse> <200801250937.22051.jhb@freebsd.org> <479A6346.3050503@skyrush.com> In-Reply-To: <479A6346.3050503@skyrush.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801300855.14582.jhb@freebsd.org> Cc: Joe Peterson , jeff@FreeBSD.org Subject: Re: New KTR trace for mouse freezing/stuttering in 7.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2008 14:23:01 -0000 On Friday 25 January 2008 05:31:34 pm Joe Peterson wrote: > John Baldwin wrote: > > Hmm, when I look at that graph using schedgraphy from HEAD it just looks > > like xtrs is using up all the CPU. > > Yeah, xtrs is eating a lot of CPU, but I've never seen this affect the > mouse movement (making it really jerky) the same way on, e.g., Linux. > And the xtrs test is just a way to *reliably* make it happen. It > happens intermittently all of the time (at least every few minutes, and > often in small batches) even when the system is pretty idle... > > -Joe So it's a scheduling bug where a compute bound process is starving an interactive one basically. :) Since you are using ULE, I would try talking to Jeff (jeff@) to see if he can address this. -- John Baldwin