Ubuntu
linux package

erratic mouse behaviour after resume

Bug #641091 reported by Vladimir Prus on 2010-09-17

This bug report is a duplicate of: Bug #550625: Alps touchpad is recognized but synaptics clients and scrolling do not work. Edit Remove

This bug affects 7 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: xserver-xorg-input-mouse

Right after resume, all pointing device I have (USB mouse, touchpad, trackstick) start to act crazily.

The USB mouse almost works, except that button clicks are ignored. Both touchpad and trackstick are broken in funny ways:
- The pointer moves erratically, sometimes jumping a long distance when I move a finger
- The buttons don't appear to work
- In fact, it seems that X thinks that some buttons are pressed, because I see desktop menu randomly appear, things scrolled, windows moved, etc.

I am not exactly sure which package is responsible for this. This reliably reproduces on E6410 after each resume under Kubuntu Maverick beta (fully updated).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-input-mouse 1:1.5.0-2build1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86 Kernel Module 256.53 Fri Aug 27 21:03:42 PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4)
Architecture: i386
Date: Fri Sep 17 11:26:23 2010
DkmsStatus:
nvidia-current, 256.53, 2.6.35-21-generic-pae, i686: installed
nvidia-current, 256.53, 2.6.35-22-generic-pae, i686: installed
EcryptfsInUse: Yes
GdmLog: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
MachineType: Dell Inc. Latitude E6410
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=7fa3ac72-7f21-4ac7-94d8-ddd0426944a9 ro quiet splash
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xserver-xorg-input-mouse
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 039J7D
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/08/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn039J7D:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
peripherals:

system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-22-generic-pae

Tags:

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-17:

.proc.driver.nvidia.cards.0.txt Edit (154 bytes, text/plain; charset="utf-8")
.proc.driver.nvidia.registry.txt Edit (408 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (58.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (591 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (826 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.7 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (208 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (116.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (19.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (532.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.1 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (24.9 KiB, text/plain; charset="utf-8")
nvidia-settings.txt Edit (33.2 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (284 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-17:

FWIW, there's bios update (A05) which has "erratic mouse behaviour" among the fixes. However, installing that had no effect on this issue.

Bryce Harrington (bryce) on 2010-09-17

tags:

added: kubuntu

Revision history for this message

Michel Adar (adar-yahoo) wrote on 2010-09-17:

I see the same problem on my laptop, which happens to be the same E6410.

After resume the touchpad and pointer mouse functions extremely erratically. An external mouse works to move the cursor, but buttons are unresponsive.

I have the latest BIOS, A05 installed. I also have the latest updates for 10.10 installed. I am running the 32 bit version.

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-18:

xev log Edit (7.7 KiB, text/plain)

I've managed to run xev from text console, and seem to have confirmed my theory. There's a stream of ButtonPress and ButtonRelease events, with rate MotionNotify between them. And surely, I only tried to move a cursor.

Is there anything further I can check?

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-18:

Further bits of info.

1. Using i8042.nomux and i8042.reest on kernel command line does not fix this.
2. This time around, external mouse buttons do work, so I've looked at dmesg and found these additional messages:

[1266874868.433383] psmouse.c: GlidePoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[1266874868.945985] psmouse.c: resync failed, issuing reconnect request
[1266874870.465631] psmouse.c: GlidePoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[1266874870.976315] psmouse.c: resync failed, issuing reconnect request
[1266874874.950429] psmouse.c: GlidePoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[1266874875.463905] psmouse.c: resync failed, issuing reconnect request
[ 342.525807] psmouse.c: GlidePoint at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
[ 343.035419] psmouse.c: resync failed, issuing reconnect request

3. If I do
modprobe -r psmouse
modprobe psmouse

both the trackstick and touchpad operate normally. Of course, this is merely an ugly workaround.

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-18:

Further bits of info.

1. Using i8042.nomux and i8042.reest on kernel command line does not fix this.
2. This time around, external mouse buttons do work, so I've looked at dmesg and found these additional messages:

3. If I do
modprobe -r psmouse
modprobe psmouse

both the trackstick and touchpad operate normally. Of course, this is merely an ugly workaround.

Revision history for this message

Vladimir Prus (vladimir-prus) wrote on 2010-09-18:

Following the advice at http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint, I have created a file /etc/pm/config.d/01reload_mouse with the following content:

SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"

And this fixes the issue. I guess the remaining questions are:

1. Is this the best way to force a module reload after resume?
2. Should this somehow be automatically enabled on E6410?
3. Is this acceptable solution, or psmouse should not lost sync in the first place, ever?

Revision history for this message

Christophe Dumez (hydr0g3n) wrote on 2010-09-18:

Note that I have the exact same issue on a E4310. This is not specific to E6410.

Also, it was working fine a few days ago and was broken by a recent package update in Maverick (I don't know which one exactly).

Revision history for this message

Christophe Dumez (hydr0g3n) wrote on 2010-09-18:

#10

This is a kernel issue. The last kernel to work is:
2.6.35-20-generic

The breakage was introduced in v2.6.35-21-generic. I hope this helps.

affects:

xserver-xorg-input-mouse (Ubuntu) → linux (Ubuntu)

Revision history for this message

Christophe Dumez (hydr0g3n) wrote on 2010-09-18:

#11

Note that there are several reports regarding touchpad issues with *-21 and *-22 kernels:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641719
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/641320
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/639894

Revision history for this message

koso (koso) wrote on 2010-09-20:

#12

I think this bug is a symptom of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642421

Maybe manual loading of modules will help...

Launchpad Janitor (janitor) on 2011-08-30

Changed in linux (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #550625 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

erratic mouse behaviour after resume

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package