From owner-freebsd-stable@FreeBSD.ORG Fri Feb 29 13:30:49 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 C16C510656C7 for ; Fri, 29 Feb 2008 13:30:49 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 50A3C8FC1D for ; Fri, 29 Feb 2008 13:30:49 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59]) by QMTA10.westchester.pa.mail.comcast.net with comcast id vQdE1Y00Z1GhbT85A01b00; Fri, 29 Feb 2008 13:20:14 +0000 Received: from discordia ([24.61.189.203]) by OMTA07.westchester.pa.mail.comcast.net with comcast id vRLk1Y00M4PktZC3T00000; Fri, 29 Feb 2008 13:20:45 +0000 X-Authority-Analysis: v=1.0 c=1 a=c5sTgUsrrxMA:10 a=uq_60wfpfT0ZdR1PFckA:9 a=qeTWze4-FPtvoFp7cYQ4-uchzCsA:4 a=ziFrdkHw70AA:10 Received: by discordia (Postfix, from userid 103) id D319C1636F9; Fri, 29 Feb 2008 08:20:44 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id B18511636F8; Fri, 29 Feb 2008 08:20:33 -0500 (EST) Message-ID: <47C805FE.5010607@FreeBSD.org> Date: Fri, 29 Feb 2008 08:17:50 -0500 From: Coleman Kane Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20080123) MIME-Version: 1.0 To: Dominic Fandrey References: <47C6FDD0.2040902@mbnet.fi> <200802281631.07844.jkim@FreeBSD.org> <47C7C611.2000609@bsdforen.de> <47C7F6D2.2000504@FreeBSD.org> <47C7F7B2.3020505@bsdforen.de> <47C7F8AE.5000506@FreeBSD.org> <47C7FC0F.7010905@bsdforen.de> <47C7FD5B.2040102@FreeBSD.org> <47C80490.9080600@bsdforen.de> In-Reply-To: <47C80490.9080600@bsdforen.de> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Teemu Korhonen , Kris Kennaway , freebsd-stable@FreeBSD.org, freebsd-x11@FreeBSD.org, Jung-uk Kim Subject: Re: jerky mouse still in 7.0-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Feb 2008 13:30:49 -0000 Dominic Fandrey wrote: > Kris Kennaway wrote: >> Dominic Fandrey wrote: >>> Kris Kennaway wrote: >>>> Well it doesn't rule it out. X may be introducing latencies that >>>> are causing your mouse to lose sync or something. >>> >>> It's not the mouse that hangs. >>> It's the only thing that works, >>> everything else hangs when I combine moused/X. This issue doesn't >>> exist on all my systems, though. It existed on my old Thinkpad >>> (Pentium-m 1.3 GHz), it exists on my new notebook (Core2 Duo with >>> 2.4 GHz), but it doesn't exist on my P4 with 1.6 GHz. >>> >>> Key entries, animations, they all just pile up somewhere and happen >>> all at once when I start using the mouse. To watch a movie I have to >>> keep the mouse moving all the time. >>> >>> It's not a general X and mouse problem, because without moused in >>> between everything works fine. I think at some point in time a bug >>> was either introduced in moused, or in my opinion more likely, in >>> the sysmouse protocol implementation in X. >> >> Could also be an interrupt issue. Either way it's still a different >> issue to the ones in this thread. > > I always thought it's about the same thing and people were just > imprecise in their perception. The P4 used to be affected by this, > too. This changed somewhere around RC1, I think. Since all of my > machines had encountered the problem since I switched them to > RELENG_7, I thought my problem was very common and it's the one > everyone is talking about. Perhaps this is related to the CX / cpu idle level problems we've been experiencing on a lot of hardware? What is the output of "sysctl -a | grep cx" on your system? -- Coleman