Mouse hangs for a few seconds after update to edgy

Bug #65649 reported by KenSentMe
6
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since i updated to Edgy every few minutes my mouse hangs and i can't control it through my touchpad. This only lasts a few seconds and then i can resume mousing. There's no abnormal systemactivity and i don't get any error messages (at least i can't find any).

In Dapper the touchpad worked fine.

magilus (magilus)
Changed in xserver-xorg-input-synaptics:
status: Unconfirmed → Confirmed
Revision history for this message
Andreas Løhre (alohre) wrote :

error message from dmesg:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1

Revision history for this message
KenSentMe (jeroen-vandenieuwenhof) wrote :

I have this error in my dmesg too:

[17180499.668000] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1

Revision history for this message
Andreas Løhre (alohre) wrote :

There seems to be some info here:

http://kerneltrap.org/node/2199/print

"Check your mouse cable. If this only happens when you move your mouse in a
certain way, fix the mouse cable or replace the mouse.

Check your kernel and harddisk settings. This message can also happen when
the mouse interrupt is delayed more than one half of a second. Make sure DMA
is enabled for your harddrive and CD-ROM. Kill your ACPI/APM battery
monitoring applet. Try disabling ACPI, frequency scaling. Make sure your
time is ticking correctly, often with frequency scaling it gets unreliable.
Even if you're using the ACPI PM Timer as a clock source - actually this
often leads to the above problem. "

It might be something to this, as the battery monitor now finally works for me in edgy, it did not in dapper - and the synaptics worked in dapper, but does not in edgy.

Revision history for this message
Andreas Løhre (alohre) wrote :

And this seemed to solve the problem. adding acpi=off to the running kernel in menu.lst solved the problem on my laptop, so this seems to be a kernel bug.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Andreas, this may be a kernel bug, but only if the machine on which the error occurred supports ACPI (if the machine supports ACPI, then is likely a kernel bug, we'll direct it there; if it doesn't, we'll either mark the bug as rejected or request thismachine be blacklisted for ACPI). Either way, we need more info.

Can you please attach the output of the following commands?

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to attach, there will be a lot of output. Also please be sure to run with sudo, these commands need root privileges to obtain required info.

Thanks!

Changed in xserver-xorg-input-synaptics:
status: Confirmed → Needs Info
Revision history for this message
Peter Whittaker (pwwnow) wrote :

Closing (marking as rejected) based on lack of feedback.

Changed in xserver-xorg-input-synaptics:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.