Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Feb 2008 13:40:59 +0100
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Dominic Fandrey <kamikaze@bsdforen.de>
Cc:        Teemu Korhonen <teemu.korhonen@mbnet.fi>, freebsd-x11@FreeBSD.org, freebsd-stable@FreeBSD.org, Jung-uk Kim <jkim@FreeBSD.org>
Subject:   Re: jerky mouse still in 7.0-RELEASE
Message-ID:  <47C7FD5B.2040102@FreeBSD.org>
In-Reply-To: <47C7FC0F.7010905@bsdforen.de>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
Dominic Fandrey wrote:
> Kris Kennaway wrote:
>> Dominic Fandrey wrote:
>>> Kris Kennaway wrote:
>>>> Your problem has different symptoms, so not entirely surprising that 
>>>> it doesn't help :)  Sounds more like that your mouse just isn't 
>>>> working properly with moused.
>>>
>>> Oh, it works fine on the console. Only the combination moused/X clashes.
>>
>> 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.

OK, that was unclear from your initial wording.

 > 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.

Kris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47C7FD5B.2040102>