Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Solved] psmouse.ko lost syncronization is on-going bug.

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
JanPenguin
Posts: 136
Joined: 2011-01-16 13:00

[Solved] psmouse.ko lost syncronization is on-going bug.

#1 Post by JanPenguin »

Kernel is 2.6.32-5-amd64
I upgraded to 2.6.39.

psmouse.ko module fails to handle some PS/2 mouse models.. 2.6.39 has less error messages than 2.6.32-5. But, it looses mouse coordinates often which triggers Xorg window manager go out of control. Only solution I found is to replace PS/2 mouse with a USB one. :)

Nov 16 15:13:19 theblue kernel: [275921.510266] psmouse.c: Wheel Mouse at
isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 16 22:43:26 theblue kernel: [293066.497048] psmouse.c: Wheel Mouse at
isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
If you have above messages and Xorg goes wild, I suggest getting a USB mouse. How many hours I had spent? Hmm..

You can check psmouse's options 'more or cat' /sys/module/psmouse/parameters/*
The below is the default options.

Code: Select all

force_elantech N
proto  auto
rate 100
resetafter 5
resolution 200
resync_time 0
smartscroll Y
If playing with the options solve the bug, it will be great. You don't need to buy another mouse.
To pass the options to psmouse module next booting, make a psmous.conf file in /etc/modprobe.d directory.

Code: Select all

options psmouse proto=imps rate=60 smartscroll=0
Last edited by JanPenguin on 2011-11-18 09:05, edited 3 times in total.

User avatar
fluxer
Posts: 70
Joined: 2011-03-12 00:52
Location: Bulgaria

Re: A serious bug of fluxbox - CPU overloading.

#2 Post by fluxer »

This had never happen on Debian Squeeze (stable). I've used Wheezy (testing) mainly until 2-weeks or so and also no trouble there. I'm fluxbox user for quite some time now and never faced that. Also I can't help you much but probably you should ask on the fluxbox irc or mailinglist, for more info visit http://fluxbox.org/help.
How YOU can help Debian! Linux HOWTOs Aliens Bash Tutotial

GNU/Linux does not stop you from doing stupid things, because that would also stop you from doing clever things.

Image

User avatar
Job
Posts: 813
Joined: 2006-12-30 20:20
Location: no clue
Contact:

Re: A serious bug of fluxbox - CPU overloading.

#3 Post by Job »

I never faced this issue and I exclusively use fluxbox on testing (desktop) and sid (laptop). Maybe something when wrong during your installation. I will remove fluxbox and add it again.
#aptitude install life
--------------------------------------------------------------------------------------------------------------
Debian 12 - FreeBSD

JanPenguin
Posts: 136
Joined: 2011-01-16 13:00

Re: mouse over screen edges makes fluxbox go wild

#4 Post by JanPenguin »

fluxbox 1.3.x - installed by source build few weeks ago
xcompmgr

I thought there is mouse related bug. So I removed 'Machintosh mouse button emulation"
My FC200R keyboard - 87 keys - has usb firmware that it has mouse and keyboard. The manufacturer is very lazy.
The keyboard name is "Cypress USB Keyboard" by xinput probe.

It looked like this.

Code: Select all

 
$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
|    ↳Cypress USB Keyboard
⎜   ↳ ImPS/2 Generic Wheel Mouse              	id=9	[slave  pointer  (2)]
⎜   ↳ Macintosh mouse button emulation        	id=10	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Cypress USB Keyboard           	id=8	[slave  keyboard (3)]
I connected the keyboard with the PS/2 adapter. Below is screen dump at the moment

Code: Select all

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ImPS/2 Generic Wheel Mouse              	id=9	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=8	[slave  keyboard (3)]
When fluxbox goes wild, there are flooding error messages.

Code: Select all

error 4 request 54 minor serial 1253002
I found almost identical error report on the net today.

Code: Select all

VastOne wrote:
Testing it on Xfce 4.8 ... Seems to be working well ... getting the following error message that I cannot make heads or tails from
error 3 (Unknown) request 20 minor 0 serial 8963
error 3 (Unknown) request 15 minor 0 serial 8964
Yep, working on that. It happens on CreateNotify events for certain windows. It happens when the X server sends a non-window XID, or override_redirect is set. Chromium tabs cause this when you drag them. It's nothing to worry about though, it's just the X server getting mad. Also, glad to hear it works well on XFWM. 
I'll stop using xcompmgr and see how it works out.

The mouse cursor on edges triggers flooding events that fluxbox can't handle.

JanPenguin
Posts: 136
Joined: 2011-01-16 13:00

Re: mouse over the toolbar makes fluxbox go wild

#5 Post by JanPenguin »

Code: Select all

Nov  9 19:06:10 theblue kernel: [220157.226257] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 10 02:18:44 theblue kernel: [242129.862072] psmouse.c: bad data from KBC - timeout
Nov 10 02:18:51 theblue kernel: [242136.622229] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Nov 10 14:59:33 theblue kernel: [ 2305.553678] psmouse.c: bad data from KBC - timeout
Nov 10 14:59:37 theblue kernel: [ 2309.895548] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Nov 10 15:02:10 theblue kernel: [ 2462.603385] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 10 15:27:19 theblue kernel: [ 3968.514790] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 10 15:52:39 theblue kernel: [ 5486.419763] psmouse.c: bad data from KBC - timeout
Nov 10 15:52:56 theblue kernel: [ 5503.795110] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 10 16:39:33 theblue kernel: [ 2092.463906] psmouse.c: bad data from KBC - timeout
Nov 10 16:39:33 theblue kernel: [ 2093.014290] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
$ uname -a

Code: Select all

Linux theblue 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64 GNU/Linux
Okay, digging it seems this is a common hardware problem that Windows
solves by ignoring: https://bugzilla.kernel.org/show_bug.cgi?ida05

Linux does too since 2.6.34:

$ git describe 6b9d363c49d22395d0cf8729c5963f83cfbb6d69
v2.6.34-rc1-31-g6b9d363
:!: I'll upgrade kernel and will see.

JanPenguin
Posts: 136
Joined: 2011-01-16 13:00

Re: mouse over the toolbar makes fluxbox go wild

#6 Post by JanPenguin »

I upgaded kernel to 2.6.39.

It still has the bug. It stopped spamming messages like before but when it appears in kernel log file, Xorg goes wild.

Code: Select all

Nov 16 15:13:19 theblue kernel: [275921.510266] psmouse.c: Wheel Mouse at
isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Nov 16 22:43:26 theblue kernel: [293066.497048] psmouse.c: Wheel Mouse at
isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
My last attempt was to adjust options of psmouse module.
I changed default value of options:
rate (100 to 60), resolution (200 to 1200), smartscroll (Y to N)

I'll buy another mouse if this solution fails again. :evil:

Code: Select all

$ more /sys/module/psmouse/parameters/*
/sys/module/psmouse/parameters/force_elantech
N
/sys/module/psmouse/parameters/proto
ImPS/2
/sys/module/psmouse/parameters/rate
60
/sys/module/psmouse/parameters/resetafter
5
/sys/module/psmouse/parameters/resolution
1200
/sys/module/psmouse/parameters/resync_time
5
/sys/module/psmouse/parameters/smartscroll
N

Post Reply