Trackpad mouse pointer freezes shortly after login; requires module unload/reload

[Ryan Reich]

I have an Asus EeePC 1005-HA and am running Oneiric. Shortly after every login, my mouse stops responding entirely, and can only be revived either by logging out and back in (which is futile) or unloading/reloading the psmouse kernel module. Steps to reproduce:

1. Log in
2. Perform normal activities for maybe five minutes, possibly only thirty seconds.
3. The mouse will stop responding. This seems to be slightly correlated with switching windows or Firefox tabs.

After the workaround, the mouse never freezes again until I log out and back in. Sometimes, though, the tapping or drag-scrolling feature stops working without the pad itself freezing, and this requires another module cycle.

Looking at `dmesg` tells me that there are a number of diagnostics:

psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1

that seem to be produced at that time. I don't know if this is a kernel bug or not; I am attaching the appropriate logs.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-13-generic 3.0.0-13.22
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ryanr 1689 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 44'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,10438398,00100004'
   Controls : 10
   Simple ctrls : 6
Date: Sat Nov 19 09:52:52 2011
HibernationDevice: RESUME=UUID=6ec489d5-eaed-467c-80f5-40f23f065db2
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: ASUSTeK Computer INC. 1005HA
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=c8c14a8c-9eb7-44da-b7fb-8db3db84b8fa ro quiet splash pcie_aspm=force vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic N/A
 linux-backports-modules-3.0.0-13-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-11-08 (11 days ago)
dmi.bios.date: 04/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd04/18/2011:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

[Ryan Reich (ryan-reich)]

I tested this with the kernel 3.2.0-030200rc2-generic, and I got the pointer freeze just the same. So either it's still broken upstream, or it's not a kernel bug. (You will have to decide which; I can't.)

[Ryan Reich (ryan-reich)]

This is an xorg driver issue: I have downgraded to the version of xserver-xorg-input-synaptics used in Natty, where I did not have this problem, and it has gone away. (That version is 1.3.99+git20110116.0e27ce3a-0ubuntu12; presumably I was using 1.4.1-1ubuntu2 before.) Therefore, the bug is in xserver-xorg-input-synaptics-1.4.1, not the kernel.

[penalvch (penalvch)]

Ryan Reich, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect <replace-with-bug-number>

[Ryan Reich (ryan-reich)]

Thanks for following up on this. Actually, it seemed to stop being a problem in the next release, so you may as well mark it fixed.

[penalvch (penalvch)]

Ryan Reich, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/892551/comments/6 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.