Bug 8740 - Synaptics Touchpad lost sync and becomes unusable
Synaptics Touchpad lost sync and becomes unusable
Status: REOPENED
Product: Drivers
Classification: Unclassified
Component: Input Devices
All Linux
: P1 normal
Assigned To: drivers_input-devices
:
Depends on:
Blocks: 9147 56331
  Show dependency treegraph
 
Reported: 2007-07-12 09:55 UTC by Chris Desjardins
Modified: 2015-03-23 14:07 UTC (History)
17 users (show)

See Also:
Kernel Version: 3.2.20
Tree: Mainline
Regression: Yes


Attachments
legolas558.devices (1.08 KB, text/plain)
2007-10-12 04:39 UTC, Daniele C.
Details

Description Chris Desjardins 2007-07-12 09:55:06 UTC
Most recent kernel where this bug did not occur: 2.6.22-1.686 (Trunk Kernel)

Distribution: Debian Unstable 

Hardware:
lontra@debian:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
05:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
05:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01)
05:06.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832
05:06.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
05:06.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
05:06.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
05:06.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
Hardware Environment: Output from lspci


Problem Description:
When using my synaptics touchpad in X my mouse becomes unusable either freezing or jumping around the screen.  Originally this seemed to be related to downloading at high rates now it seems to be very sporadic but occurring much more frequently perhaps when the CPU is under a high load.  When my mouse freezes it takes a few seconds to resync and then becomes usuable again until it freezes again.    My mouse will become unusable several times in 10 minutes essentially rendering it unusable.  This occurs under a variety of distributions but appears to have only started to occur since the 2.6.18 series.  

Here is the output from dmesg:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: Failed to reset mouse on isa0060/serio1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: issuing reconnect request
input: PS/2 Generic Mouse as /class/input/input10
psmouse.c: Failed to enable mouse on isa0060/serio1
psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: issuing reconnect request
psmouse.c: failed to re-enable mouse on isa0060/serio1
psmouse.c: resync failed, issuing reconnect request
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)

This doesn't seem to be related to bcm43xx becauses when i remove the module (via rmmod bcm43xx) this problem still occurs.

Steps to reproduce:
Seems to be sporadic but when I am visiting gmail.com it always happens.
Comment 1 Dmitry Torokhov 2007-07-12 11:28:43 UTC
Does it help if you boot with "ec_intr=2" on the kernel command line? What about acpi=off?
Comment 2 Chris Desjardins 2007-07-12 12:08:39 UTC
Neither ec_intr=2 nor acpi=off helped.  The problem was still occurring.  FYI, the laptop I am using is a Lenovo 3000 n100.  

Thanks for the prompt response!
Chris  
Comment 3 Dmitry Torokhov 2007-07-12 12:49:16 UTC
Ok, so you are saying that 2.6.17 was ok but since 2.6.18 things went bad? COuld you try narrow it down to a specific 2.6.18-rcX release?
Comment 4 Chris Desjardins 2007-07-12 12:57:47 UTC
Sorry.  Post-2.6.18 it seemed to go bad.  However, I just bought this laptop a few months ago and the 2.6.18 worked relatively well.  I didn't test any kernel earlier than 2.6.18.  The kernel 2.6.18-4-686 in Debian Etch worked well here but because of lack of support for brightness and other hardware I upgraded to the 2.6.22-1 kernel.  I experienced some issues with losing sync bytes in 2.6.18-4 but not like in the 2.6.22-1 kernel.  It froze up but very rarely.       
Comment 5 Chris Desjardins 2007-07-12 12:59:10 UTC
Also I do not believe this is an issue of broken hardware as my laptop is very new.  
Cheers,
Chris
Comment 6 Dmitry Torokhov 2007-07-17 08:20:03 UTC
Hmm. Do you really have external mouse attached? Or do you have only touchpad and kernel is confused?
Comment 7 Chris Desjardins 2007-07-17 13:54:32 UTC
On Tuesday 17 July 2007 10:14:54 am you wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8740
>
>
>
>
>
> ------- Comment #6 from dtor@insightbb.com  2007-07-17 08:20 -------
> Hmm. Do you really have external mouse attached? Or do you have only
> touchpad and kernel is confused?

I have a Synaptics Touchpad and when my mouse becomes unresponsive I use a usb 
mouse.

Comment 8 Dmitry Torokhov 2007-07-17 13:58:02 UTC
No, I mean external PS/2 mouse?
Comment 9 Chris Desjardins 2007-07-17 14:13:18 UTC
On Tuesday 17 July 2007 03:52:52 pm you wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8740
>
>
>
>
>
> ------- Comment #8 from dtor@insightbb.com  2007-07-17 13:58 -------
> No, I mean external PS/2 mouse?

There is no external PS/2 mouse.  I just have my built-in Synaptics Touchpad 
and the usb mouse.  I don't believe it's being confused by the mouse as this 
is occurring before I insert the mouse into the usb slot.  

Comment 10 Dmitry Torokhov 2007-07-17 19:38:00 UTC
However the kernel managed to detect one ;) Could you post your /proc/bus/input/devices?
Comment 11 Chris Desjardins 2007-07-17 19:45:05 UTC
On Tuesday 17 July 2007 09:32:49 pm you wrote:
> /proc/bus/input/devices


[lontra@localhost ~]$ cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse1 event1
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c03d Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:1d.3-1/input0
S: Sysfs=/class/input/input3
H: Handlers=mouse2 event3
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/class/input/input4
H: Handlers=kbd event4
B: EV=40001
B: SND=6

I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=button_power/button/input0
S: Sysfs=/class/input/input5
H: Handlers=kbd event5
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/class/input/input6
H: Handlers=event6
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/class/input/input7
H: Handlers=kbd event7
B: EV=3
B: KEY=100000 0 0 0

Comment 12 Dmitry Torokhov 2007-07-19 07:48:37 UTC
OK, what about booting with i8042.nomux? Does the box have external PS/2 ports?
Comment 13 André 2007-09-26 12:51:03 UTC
Hello, I have the same problem on a Lenovo 3000 C200.
Here my bug report http://bugs.gentoo.org/show_bug.cgi?id=192314 (with some additional information: dmesg, /proc/bus/input/devices file, emerge --info...)

I tried with i8042.nomux=1 (see my dmesg 
-> http://bugs.gentoo.org/attachment.cgi?id=131233&action=view )

It's seem to be better with "nomux=1" but I still lost sync (see the new
dmesg).

I don't have any external PS/2 ports.
Thank you.
Comment 14 Daniele C. 2007-10-12 04:30:12 UTC
I do have the same problem, but I have a differnet hardware (see http://gentoo-wiki.com/HARDWARE_Maxdata_Pro_7000_DX which I am maintaing)

In my case I am 99% sure that i8042.nomux=1 is totally working it around; the bug is coupled with this old one
http://bugzilla.kernel.org/show_bug.cgi?id=9147

These laptops do have PS2 plugs but they're hard-wired to the keyboard and mouse; theorically, if I would open it I could wire an external keyboard. I have also heard that there are more than the usual 2 PS2 plugs, but I am not sure about this.

My feeling is that ACPIPNP is causing the kernel to "eat" some mouse/keyboard IRQs; I am available for further testing.

Note: I do have a good amount of C programming experience (for what matters here: sockets, low level hardware, data crunching etc.) but I am relatively new to linux (2 years), and absolutely new to kernel hacking (installed Gentoo on June) - I should be able to understand and try some more technical testcases
Comment 15 Daniele C. 2007-10-12 04:39:47 UTC
Created attachment 13128 [details]
legolas558.devices

my /proc/bus/input/devices - note that I have a Synaptics PS/2 Touchpad (integrated)
Comment 16 Daniele C. 2007-10-12 06:05:40 UTC
I do use ipw2100 for the wireless LAN and I can remember the problem did not happen when the module was not loaded (tested only with 2.6.22), e.g. when the wireless adaptor was not ON.
Comment 17 Erik Boritsch 2007-11-17 11:55:28 UTC
I am confirming both the issue and the workaround i8042.nomux=1 on my Acer Travelmate 243LC. This problem is clearly an ACPI issue: the symptoms are shown only if at least one of the following acpi modules is loaded: ac, battery, thermal. If I unload all three of them, my touchpad doesn't lose sync.
Comment 18 Len Brown 2007-11-23 20:21:54 UTC
Daniele, Erik,
In comment #2, Chris (the submitter of this bug) noted
that the issue at hand does not go away with "acpi=off".
By definition, that means this bug report has nothing to do with ACPI.

If you have an issue which does go away with "acpi=off",
then I invite you to submit a new sighting in the ACPI category,
or contribute to an existing one, such as bug #9147.
Comment 19 Daniele C. 2007-11-24 11:08:59 UTC
Using acpi=off does nothing. Only i8042.nomux=1 does work around the bug
Comment 20 Chris Desjardins 2007-11-24 14:59:24 UTC
I have managed to track down the cause of my Synaptics touchpad issue.  My problem is associated with the orinoco_cs module or a related module.  When I use my onboard wireless card using ndiswrapper I do not experience this problem but when I use my Orinoco card which uses the orinoco_cs module I am unable to surf the internet, download, etc. and use my touchpad. 
Comment 21 Chris Desjardins 2007-11-24 15:01:03 UTC
This is still present on the 2.6.23 kernel in Fedora too.  
Comment 22 Bogdan 2008-04-10 01:16:46 UTC
For me the problem is present for every kernel from 2.6.22 - 2.6.24. I have discovered recently that the problem only exists on the 32-bit x86 architecture, the 64-bit has no such problem. I a this on both 32-bit and 64-bit editions of Fedora and Ubuntu.
Comment 23 Daniele C. 2008-08-03 06:41:08 UTC
The current workaround is still i8042.nomux=1, can somebody please confirm this?
Comment 24 André 2008-08-03 07:27:15 UTC
It didn't resolve the problem completely when I tried on my 2.6.21 kernel (http://bugs.gentoo.org/show_bug.cgi?id=192314#c6).
I'm now using a gentoo-sources-2.6.25 and I haven't seen the problem since.

However I had some kernel or X freeze (can't remember) but I don't know if it's related to this kernel option.

I also saw that someone was complaining for the same problem using Windows XP.
On LDLC (french) (I bough mine there as well):
Comment title: "Affichage pointeur souris laisse à désirer".
Link: http://www.ldlc.com/critiques/PB00047768-1/lenovo-3000-c200-intel-core-2-duo-t5500-512-mo-512-mo-offert-80-go-15-tft-dvd-rw-wi-fi-g-wxph.html
Comment 25 Andres Mujica Ubuntu BugSquad 2008-08-10 18:28:17 UTC
Hi all, i've linked the LP #119194 with this bug as it seems these are the same one,

https://bugs.launchpad.net/linux/+bug/119194
Comment 26 Andres Mujica Ubuntu BugSquad 2008-08-10 18:30:01 UTC
And with LP bug #34501

https://bugs.launchpad.net/linux/+bug/34501

Thanks again
Comment 27 Daniele C. 2008-08-11 23:55:45 UTC
I am not sure if this bug is linked to LP #119194, I have never seen parity errors on my case
Comment 28 Joachim Breitner 2008-12-20 09:33:56 UTC
I have to add that this happens with 2.6.27 on a T400. Setting i8042.nomux=1does _not_ help in my case.
Comment 29 Joachim Breitner 2008-12-20 09:37:43 UTC
Another hint I found somewhere was using i8042.dumbkbd=1, but that did not help here either.
Comment 30 Joachim Breitner 2008-12-20 11:57:56 UTC
I did get some relief, it seems, by setting
# echo -n 1 > /sys/devices/platform/i8042/serio1/resetafter

Of course, this is just a work-around.
Comment 31 Daniele C. 2008-12-28 02:09:23 UTC
I am *NO MORE* using i8042.nomux=1 with kernel 2.6.27-7 (Ubuntu Intrepid Ibex), it seems having been fixed either by activation of nomux through a DMI match or in the kernel source code somewhere.

Can somebody please confirm that i8042.nomux=1 is no more necessary to workaround this bug?
Comment 32 Daniele C. 2009-01-24 09:29:45 UTC
(In reply to comment #31)
The i8042.nomux=1 kernel parameter is still necessary.

Perhaps we need a patch...
Comment 33 Daniele C. 2009-01-24 12:55:54 UTC
(read on https://bugs.launchpad.net/linux/+bug/119194/comments/34)

perhaps acpi_osi=Linux can work around the problem (in place of i8042.nomux=1)
Comment 34 Joachim Breitner 2010-01-06 12:17:16 UTC
This could be a duplicate of #12577, whose fix was just included in the Debian linux kernel. I’ll report here if it works for me with that.
Comment 35 Joachim Breitner 2010-01-07 12:20:13 UTC
Unfortunately not. The patch (http://svn.debian.org/wsvn/kernel/dists/trunk/linux-2.6/debian/patches/features/all/input-alps-add-interleaved-protocol-support.patch?rev=14799&sc=1) only patches alps, but here, on my ThinkPad T400, the synaptics driver grabs the device. Maybe a similar patch for the synaptics driver has to be produced?
Comment 36 taur 2010-06-08 09:49:35 UTC
I can confirm that acpi_osi=Linux resolves the issue on x64 ubuntu 10.04 kernel 2.6.32-22
Comment 37 Dmitry Torokhov 2010-06-08 16:34:18 UTC
If changing osi response indeed fixes the issue then ACPI guys will have to take a look here.
Comment 38 Zhang Rui 2010-10-22 03:03:36 UTC
Hi, all,
does the problem still exist in the latest upstream kernel?
Comment 39 Joachim Breitner 2010-10-23 10:37:27 UTC
On
$ uname -a
Linux kirk 2.6.36-rc6-amd64 #1 SMP Mon Oct 4 09:56:45 UTC 2010 x86_64 GNU/Linux

I still observer some issues:

[   52.011328] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   52.011332] psmouse.c: issuing reconnect request
[  217.087051] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4
[  217.087058] psmouse.c: issuing reconnect request
[  287.894903] psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 4 bytes away.
[  288.409026] psmouse.c: resync failed, issuing reconnect request
[  460.823615] psmouse.c: bad data from KBC - timeout
[  460.835107] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4
[  460.835113] psmouse.c: issuing reconnect request
[  466.644117] psmouse.c: Failed to enable mouse on synaptics-pt/serio0

when having both trackpoint and touchpad enabled. It seems the problem occurs less than earlier (but this is just my impression), but it is definitely still present.
Comment 40 Len Brown 2011-01-18 07:36:08 UTC
> this bug did not occur: 2.6.22-1.686

marking as a regression
Comment 41 Zhang Rui 2011-03-21 07:30:35 UTC
the problem still exists in the latest upsteam kernel, right?
Comment 42 Zhang Rui 2011-04-19 07:41:52 UTC
bug closed as there is no response from the bug reporter.
please re-open it if the problem still exists in the latest upstream kernel.
Comment 43 Joachim Breitner 2012-06-28 14:15:27 UTC
On 3.2.0, I still have this problem:

[   55.444165] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   55.446370] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   55.448494] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.420802] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.423256] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.423258] psmouse serio1: issuing reconnect request

But only once since system start so far. I’ll observe it some more...

(It seems I lack rights to re-open the bug.)
Comment 44 Joachim Breitner 2012-06-28 14:21:06 UTC
Yes, occurs more often, now also with different text:

[   55.444165] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   55.446370] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   55.448494] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.420802] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.423256] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[   76.423258] psmouse serio1: issuing reconnect request
[  389.906979] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[  389.909379] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[  389.911666] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[  389.943244] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[  389.945504] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[  389.945507] psmouse serio1: issuing reconnect request
[  650.377282] psmouse serio1: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away.
[  650.888206] psmouse serio1: resync failed, issuing reconnect request
Comment 45 Nikolay 2012-09-30 13:27:26 UTC
I have same trouble. Notebook Samsung 350u2b. Archlinux.

Sometimes touchpad not workinkg.

That happens when one finger in the lower right corner, and the other finger on
the center of the touchpad.


$ xinput list | grep Touchpad
⎜   ↳ ETPS/2 Elantech Touchpad                  id=12   [slave  pointer  (2)]

$dmesg
[ 4335.879836] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at
byte 6
[ 4335.908340] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver
resynced.
[ 5018.411486] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at
byte 6
[ 5018.423943] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver
resynced.
[ 5029.876019] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at
byte 6
[ 5029.897982] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver
resynced.

Solution, Just reload psmouse module.
$rmmod psmouse
$modprobe psmouse

Kernel:
$uname -a
Linux samsung 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64
GNU/Linux
Comment 46 Dmitry Torokhov 2012-10-01 16:21:45 UTC
(In reply to comment #45)
> I have same trouble. Notebook Samsung 350u2b. Archlinux.
> 
> Sometimes touchpad not workinkg.
> 
> That happens when one finger in the lower right corner, and the other finger on
> the center of the touchpad.
> 
> 
> $ xinput list | grep Touchpad
> ⎜   ↳ ETPS/2 Elantech Touchpad                  id=12   [slave  pointer  (2)]

This is not Synaptics but Elantech touchpad. Could you please open a separate bug report for this?
Comment 47 Aaron Lu 2013-02-28 02:26:35 UTC
I'm moving this bug from acpi to drivers/input-dev, please correct me if this is not the right component, thanks.
Comment 48 Alexander Mezin 2013-03-15 10:53:57 UTC
I have the same problem on kernel 3.8.3. I found this patch:
http://thread.gmane.org/gmane.linux.kernel.input/25599
And it solves the problem. Why it still isn't merged?
Comment 49 Merlijn Wajer 2013-05-20 15:44:14 UTC
The patch from comment #48 also fixes the problem for me. Would be nice to see if it can be merged.

This is my Touchpad model:

    psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd04773/0xe40000/0x5a0400, board id: 3655, fw id: 684465
Comment 50 alpine.art.de 2013-05-26 15:56:35 UTC
Since 3.9 this extremely bugs me. <3.9 only needed some seconds to get my psmouse up, but since 3.9 I get hangs during usage, may happen several times per minute - quite unusable :( Even worse it sometimes does not recover automatically and makes the whole keyboard unusable - no ctrl+alt+backspace, no shortcuts to fire up e17-everything. I need to sleep + resume my Laptop to get it working again. The first time this happened I thought I had a kernel deadlock. Good luck I just tried to get it Suspended before hard powering off...

The weird thing: I did not enable TouchPad in the kernel, I did not install synaptics xorg-driver. I only use the TrackPoint from my Lenovo L520. The touchpad can't be enabled, it's "dead". But I get these errors:

[198183.044677] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[198183.056488] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[198183.057870] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[198183.059166] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[198183.060198] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[198183.060205] psmouse serio4: issuing reconnect request
[198821.998906] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[198822.000232] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[198822.019445] psmouse serio4: TouchPad at isa0060/serio4/input0 - driver resynced.

If you think this is another issue I will open a new bug report.
Comment 51 Dmitry Torokhov 2013-06-04 16:36:46 UTC
I just merged Eric's patch and it should be in 3.10, however if there was a significant regression in 3.9 compared to 3.8 that would mean there is another issue, probably outside of the input subsystem. I wonder if you will be to try bisecting this regression.
Comment 52 Mathias Dietrich 2013-06-23 09:11:44 UTC
I also had issues with my touchpad [1] in 3.8. Therefore I tested 3.10rc7 to if the patch brought improvement. I must admit compared to 3.8 it's definitely an improvement although the issue is not fixed completely.

I still get the dmesg output [2] and I still get an unusable touchpad during heavily typing (just typing a lot a move the touchpad to reproduce). But in comparison to 3.8 it only takes 2 seconds until the touchpad works again (you just need to stop typing).

The is also this patch from google [3]. Anyone tried it yet ?




[1] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd047b3/0xb40000/0xa0000, board id: 71, fw id: 578367

[2] smouse serio4: issuing reconnect request
[  176.650713] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[  176.652089] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[  176.670212] psmouse serio4: TouchPad at isa0060/serio4/input0 - driver resynced.
[  179.109667] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[  179.118082] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[  179.119450] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[  179.124539] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[  179.140162] psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[  179.140175] psmouse serio4: issuing reconnect request

[3] https://patchwork.kernel.org/patch/2156601/
Comment 53 Mathias Dietrich 2013-06-23 13:33:30 UTC
Tested Chromium's patch [1] on Kernel 3.8, with no improvement here.

[1] https://patchwork.kernel.org/patch/2156601/
Comment 54 Mathias Dietrich 2013-07-23 19:06:07 UTC
Just a small update. I still have this issues in 3.11-rc2 on Lenovo L520.
If you need an xev.log or similar, please have a look at Ubuntu's bugreport [1], where I recently filed all these.

[1] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/896922
Comment 55 klamm2001 2013-09-06 19:05:39 UTC
ThinkPad-L520 with 3.2.0-53-generic and *still* and issue. Since 3.2.0-45 I have this problem and I have no idea how to fix it. I tried many things and none works.
Comment 56 Jon Vaughan 2014-01-29 22:08:45 UTC
I have a new Thinkpad t440s which has this issue, where the touchpad loses sync every few minutes, sometimes resyncing successfully, sometimes locking up and requiring a modprobe psmouse to get going again.  This happens with 3.11 and the latest kernel mainline 3.13.1-031301

This is being tracked under the ubuntu tracker here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268365

If you need any information, want anything tested, or if there is anything I can do to help fix this then please let me know.
Comment 57 Tom Wijsman 2014-03-16 14:59:06 UTC
Given that the other bug is closed per hardware fail, this one can be closed too.

For reference:

    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268365/comments/14
Comment 58 Synthead 2014-10-14 17:18:13 UTC
I am seeing this issue with a Latitude E7440 on Arch Linux with the default 3.16.4 kernel.

dmesg output related to this bug (systemd):

[ 6135.425681] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6135.426716] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6135.427730] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6135.430819] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.
[ 6943.621660] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6943.624732] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.
[ 6943.625690] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6943.632644] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.
[ 6943.633638] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
[ 6943.636722] psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.

uname -a:

Linux george 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/Linux

Relevant dmidecode info:

Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
        Internal Reference Designator: J1A1
        Internal Connector Type: None
        External Reference Designator: PS2Mouse
        External Connector Type: PS/2
        Port Type: Mouse Port

Handle 0x0026, DMI type 21, 7 bytes
Built-in Pointing Device
        Type: Touch Pad
        Interface: Bus Mouse
        Buttons: 2

Relevant lsmod info:

i8042                  18002  2 libps2,dell_laptop
serio                  18282  6 serio_raw,atkbd,i8042,psmouse
Comment 59 Aravind 2014-11-01 08:41:40 UTC
I recently bought an ASUS X553M laptop and have run into this problem. A few observations I would like to share:

I downloaded and installed the live Fc20 version of Fedora. It came with a kernel version of 3.11.10-301.fc20.x86_64.  The touchpad was working as a mouse - allowing cursor positioning and tapping.

After installation the broadcom 4312 14e4:4365 wifi interface was not recognized so applied the process mentioned in the broadcomm site for this adapter. The kernel version changed to 3.16.6-203.chitrai.fc20.x86_64.

Wifi worked like a charm. But the touchpad stopped working. However the touchpad now is being recognised as an ELantech touchpad and synclient shows a lot of properties of the device. Working on the touchpad leads to the "psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6" messages for every position.

I also notice that after the wifi driver was installed and kernel changed 
#rmmod psmouse  gives the following message 
rmmod: ERROR: Module psmouse is builtin.

I did a simple custom compilation to see if compiling on the required hardware platform will fix the issue. It didn't. I have not tried the patch.

Hope this helps.
Comment 60 Aravind 2014-11-01 08:43:51 UTC
The kernel version changed to 3.16.6-203.fc20.x86_64 after the wifi driver fix.
3.16.6-203.chitrai.fc20.x86_64 was the vanilla compile. Apologies for the oversight in typing.

Note You need to log in before you can comment on or make changes to this bug.