psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.

[slimbook]

353/5000
Hello,
Randomly the touchpad pointer moves to one end of the screen, and we have found that when it does message appears in dmseg:

psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.

Sometimes it happens after 10 minutes of use, sometimes it happens after 3 or 4 hours.
We have tested several computers with touchpad "Hantick", that use the both, the evdev library and the libinput library. It always happens randomly.

Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-45-generic 4.8.0-45.48
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alejandrolopez 1678 F.... pulseaudio
 /dev/snd/controlC1: alejandrolopez 1678 F.... pulseaudio
CurrentDesktop: MATE
Date: Wed Apr 5 09:39:01 2017
HibernationDevice: RESUME=UUID=49104028-270a-4546-b219-b38918f339ba
InstallationDate: Installed on 2016-04-30 (339 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SLIMBOOK
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop quiet i8042.noloop i8042.notimeout i8042.nomux psmouse.resolution=1200 psmouse.resetafter=1 psmouse.rate=50 mousedev.xres=1900 mousedev.yres=800 i8042.reset plymouth:debug drm.debug=0xe
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-45-generic N/A
 linux-backports-modules-4.8.0-45-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-11-10 (145 days ago)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: h
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name:
dmi.board.vendor: SLIMBOOK
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SLIMBOOK
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pn:pvr1.0:rvnSLIMBOOK:rn:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
dmi.product.name:
dmi.product.version: 1.0
dmi.sys.vendor: SLIMBOOK

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc5

[slimbook (slimbook)]

Hello Joseph,
I installed the kernel you told me.
The error has taken more time to reappear, but has appeared:

psmouse serio1: Explorer Mouse at isa0060 / serio1 / input0 lost synchronization, throwing 1 bytes away.

Thank you very much.

[Kai-Heng Feng (kaihengfeng)]

Please try 'psmouse.proto=bare', 'psmouse.proto=imps' or 'psmouse.proto=exps', without any other kernel parameters.

[slimbook (slimbook)]

Hello,
Thanks Kai-Heng, with "imps" and "bare" the touchpad is crazy.

I had defined the other parameters tried to fix the error. But I have deleted and put only psmouse.proto=exps

Now the touchpad works, but I still try to see if the error returns, because I think "exps" is normal mode...

[slimbook (slimbook)]

Unfortunately the problem continues.

Whenever this happens the pointer moves top of screen completely, or to the top right corner. The tocuhpad does not work if I try to move the pointer with my finger, that is, until I do not separate my finger from the touchpad.

[ 4854.804507] psmouse serio2: Explorer Mouse at isa0060/serio2/input0 lost synchronization, throwing 2 bytes away.

[Kai-Heng Feng (kaihengfeng)]

Hmm, can you explain the situation more explicitly?
Does the touchpad keeps working after the kernel message?
At what situation it doesn't work?
At waht situation it works?

[slimbook (slimbook)]

Yes, sorry:
You turn on the computer, you use it normal, and the tocuhpad works.
After 10 minutes or sometimes 1 hour, while touching the touchpad with your finger, the pointer jumps top of the screen and does not obey finger movements, until you remove your finger from the touchpad and wait for 1 second, then it works again.
The touchpad continues to work properly until after some time it does the same again.
Thank you!

[slimbook (slimbook)]

Hello
Attached dmesg file complete of today.

In breif:
dmesg | grep psmouse
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc5-lowlatency root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop psmouse.proto=exps
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc5-lowlatency root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop psmouse.proto=exps
[ 1278.574272] psmouse serio2: Explorer Mouse at isa0060/serio2/input0 lost synchronization, throwing 2 bytes away.
[14523.769979] psmouse serio2: Explorer Mouse at isa0060/serio2/input0 lost synchronization, throwing 2 bytes away.

[Jesús González (jesulinico)]

It's a serious trouble, slimbook the user who reported the bug, represents a whole brand that is making great efforts to spread free software.

[slimbook (slimbook)]

Hello, thanks jesulinico.

We actually tested these computers with Windows 10 and the touchpad does not skip after several days of use.

This is a problem with Ubuntu, I do not know what else we can facilitate so that they do not label in problem like "Incomplete, give more info".

Please, that more information is needed.

[Kai-Heng Feng (kaihengfeng)]

Hi Slimbook,

Can I get a slimbook? ;)

Do you know the touchpad manufacturer? e.g. Alps, Synaptics, Elan?

[slimbook (slimbook)]

Hello Kai-Heng,
I wrote the manufacturer at the beginning of the bug: Hantik
We can temporarily give one up for testing.
Thanks

[slimbook (slimbook)]

Sorry, "Hantick"

[Kai-Heng Feng (kaihengfeng)]

A quick google shows that Hantick sells rebranded Elan touchpad (in Chinese though) - that's why I asked this question.

Anyway, please give Linux kernel here a try: http://people.canonical.com/~khfeng/lp1679962/

[slimbook (slimbook)]

Hello,
Nothing has changed.
Attached information.
Thank you very much.

[Kai-Heng Feng (kaihengfeng)]

Hmm, I enabled all psmouse protocol detection in that one, apparently it didn't work.

Please file an upstream bug.

[slimbook (slimbook)]

Sorry, Kai_heng, I upload attached details on my previous post as "files.tar.xz"
What need you?

Do you think this random problem may be related to ubuntu not detecting the touchpad as touchpad if not as generic mouse?:
Https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625

Thank you very much.

[Kai-Heng Feng (kaihengfeng)]

Probably. Is it an HID devices in Windows 10?

[slimbook (slimbook)]

Hello

Information

ID hardware
ACPI\VEN_MSFT&DEV_0003

GUID DEV CLASS
4D36E96F-E325-11CE-BFC1-08002BE10318

ACPI\MSFT0003\4&a04c74c&0

[Kai-Heng Feng (kaihengfeng)]

Hmm, try this:

$ sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serioX/protocol'

Replace X with correct serio number.

File an upstream bug if this doesn't work.

[slimbook (slimbook)]

Hello Kay-Heng,
We do it, and the pointer is crazy, not work correctly.

[abbot (shamardin)]

I think I observe a very similar issue on ubuntu 16.04, only in my case mouse reaction to touchpad is very laggy and jumpy/choppy. It started after one of the recent kernel updates. For me linux-image-4.4.0-72-generic seems to work fine with default kernel options, linux-image-4.4.0-78-generic is broken, so it must be one of the changes between these two version which breaks this.

Syslog:

May 24 23:38:15 abbot kernel: [ 958.625194] psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away.
May 24 23:38:15 abbot kernel: [ 959.139410] psmouse serio1: resync failed, issuing reconnect request
May 24 23:38:16 abbot kernel: [ 959.676100] psmouse serio1: elantech: retrying ps2 command 0xf8 (2).
May 24 23:38:16 abbot kernel: [ 960.186792] psmouse serio1: elantech: retrying ps2 command 0x00 (2).
May 24 23:38:17 abbot kernel: [ 960.888154] psmouse serio1: elantech: retrying ps2 command 0x00 (1).
May 24 23:38:18 abbot kernel: [ 961.592132] psmouse serio1: elantech: retrying ps2 command 0x00 (0).
May 24 23:38:18 abbot kernel: [ 962.096170] psmouse serio1: elantech: ps2 command 0x00 failed.
May 24 23:38:18 abbot kernel: [ 962.096181] psmouse serio1: elantech: failed to write register 0x07 with value 0x01.
May 24 23:38:18 abbot kernel: [ 962.096183] psmouse serio1: elantech: failed to initialise registers.
May 24 23:38:18 abbot kernel: [ 962.096184] psmouse serio1: elantech: failed to put touchpad back into absolute mode.
May 24 23:38:19 abbot kernel: [ 962.803046] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x4d1f03)
May 24 23:38:19 abbot kernel: [ 962.818943] psmouse serio1: elantech: Synaptics capabilities query result 0x80, 0x14, 0x0c.
May 24 23:38:19 abbot kernel: [ 962.832728] psmouse serio1: elantech: Elan sample query result 05, 00, 85
May 24 23:38:19 abbot kernel: [ 962.894729] input: Elantech PS/2 TrackPoint as /devices/platform/i8042/serio1/input/input18
May 24 23:38:19 abbot kernel: [ 962.911950] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input17
May 24 23:38:37 abbot kernel: [ 980.879537] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
May 24 23:38:38 abbot kernel: [ 982.051838] psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
May 24 23:38:39 abbot kernel: [ 982.563469] psmouse serio1: resync failed, issuing reconnect request

[Kai-Heng Feng (kaihengfeng)]

@slimbook,

Does it support 3/4 fingers in Windows?
Does it work under -72 as @abbot says?

@abbot,
Can you also try linux kernels between -72 and -78? We can narrow down the changes we need to look at.

[V. vd. Graaf (focus4)]

I had similar problem after upgrading from Ubuntu 14.04 to 18.04 (Ubuntu 4.15.0-42.45-generic 4.15.18). I noticied that when I shut down wifi the touchpad lag is gone. Also when I turn wifi on again, the lag doesn't re-appear. After restarting my laptop the lag is back again.
Dmesg shows (after the turning wifi off and on again) an extra piece of information (although I don't know what it means):

[ 802.187333] psmouse serio1: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away.
[ 818.784094] wlp6s0: deauthenticating from 0**** by local choice (Reason: 3=DEAUTH_LEAVING)
[ 838.410647] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[ 838.540339] IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
[ 840.208690] wlp6s0: authenticate with 0*****
[ 840.610491] wlp6s0: send auth to 0**** (try 1/3)
[ 840.613821] wlp6s0: authenticated
[ 840.618291] wlp6s0: associate with 0***** (try 1/3)
[ 840.621835] wlp6s0: RX AssocResp from 0***** (capab=0x411 status=0 aid=9)
[ 840.622520] wlp6s0: associated
[ 840.645374] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready

[willdeans (william-deans)]

I have a Lenovo W530 and I am having the same problem as others describe. I found these messages from dmesg:

[ 435.029679] psmouse serio1: bad data from KBC - timeout
[ 561.787068] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
[ 724.389084] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
[ 734.832316] psmouse serio1: TrackPoint at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.

cat /etc/issue
Ubuntu 18.04.1 LTS \n \l

uname -a
Linux w530b 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Priority: "makes computer unusable".

For me turning off wifi and back on didn't help.