issues with touchpad after update

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi,

after updating system to current yesterday (kernel + userland) I noticed 
that the TouchPad in X11 is essentially unusable.
It overreacts and clicks at random. What I think is that it attempts 
"scrolling" because just by moving the pointer I notice the xterm scroll 
or windows roll-up.

If I attach an USB mouse, it works perfectly.

X11 log says:
[    96.846] (**) Option "CorePointer" "on"
[    96.846] (**) <default pointer>: always reports core events
[    96.846] (WW) <default pointer>: No Device specified, looking for one...
[    96.963] (II) <default pointer>: found Device "/dev/wsmouse"
[    96.967] (--) <default pointer>: Device: "/dev/wsmouse"
[    96.967] (==) <default pointer>: Protocol: "WSMouse"
[    96.967] (**) <default pointer>: always reports core events
[    96.967] (**) Option "Device" "/dev/wsmouse"
[    97.088] (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
[    97.088] (**) <default pointer>: ZAxisMapping: buttons 4 and 5
[    97.088] (**) <default pointer>: Buttons: 9
[    97.088] (II) XINPUT: Adding extended input device "<default 
pointer>" (type: MOUSE, id 6)
[    97.088] (**) <default pointer>: (accel) keeping acceleration scheme 1
[    97.088] (**) <default pointer>: (accel) acceleration profile 0
[    97.088] (**) <default pointer>: (accel) acceleration factor: 2.000
[    97.088] (**) <default pointer>: (accel) acceleration threshold: 4


but also:
(EE) [mi] EQ overflowing.  Additional events will be discarded until 
existing events are processed.
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit 
higher up the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
(EE) [mi] EQ overflow continuing.  100 events have been dropped.
[ 95253.888] [mi] Increasing EQ size to 1024 to prevent dropped events.
[ 95266.073] [mi] EQ processing has resumed after 121 dropped events.
[ 95266.107] [mi] This may be caused by a misbehaving driver 
monopolizing the server's resources.


however the timestamp is much later, so I don't think the latter is 
relevant.

Riccardo