Acer laptop, SYN1B7F Synaptics touchpad gets wild sometimes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,


on Acer laptop, my SYN1B7F Synaptics touchpad quite often starts acting
wild, moving and clicking and scrolling on its own. It uses HID over I2C
interface. The kernel is 4.19.0 on Debian.


This is an example of the evtest output in those moments, while I didn't
touch the pad at all:


Event: time 1622047857.609072, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42932700
Event: time 1622047857.609072, -------------- SYN_REPORT ------------
Event: time 1622047857.616372, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42939900
Event: time 1622047857.616372, -------------- SYN_REPORT ------------
Event: time 1622047857.623630, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42947100
Event: time 1622047857.623630, -------------- SYN_REPORT ------------
Event: time 1622047857.630933, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42954300
Event: time 1622047857.630933, -------------- SYN_REPORT ------------
Event: time 1622047857.638218, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42961500
Event: time 1622047857.638218, -------------- SYN_REPORT ------------
Event: time 1622047857.645786, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 489
Event: time 1622047857.645786, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 215
Event: time 1622047857.645786, type 3 (EV_ABS), code 0 (ABS_X), value 489
Event: time 1622047857.645786, type 3 (EV_ABS), code 1 (ABS_Y), value 215
Event: time 1622047857.645786, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42968700
Event: time 1622047857.645786, -------------- SYN_REPORT ------------
Event: time 1622047857.653065, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42975900
Event: time 1622047857.653065, -------------- SYN_REPORT ------------
Event: time 1622047857.660063, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 498
Event: time 1622047857.660063, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 181
Event: time 1622047857.660063, type 3 (EV_ABS), code 0 (ABS_X), value 498
Event: time 1622047857.660063, type 3 (EV_ABS), code 1 (ABS_Y), value 181
Event: time 1622047857.660063, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42983100
Event: time 1622047857.660063, -------------- SYN_REPORT ------------
Event: time 1622047857.667358, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 182
Event: time 1622047857.667358, type 3 (EV_ABS), code 1 (ABS_Y), value 182
Event: time 1622047857.667358, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 42990300
Event: time 1622047857.667358, -------------- SYN_REPORT ------------


I also noted that lots of those lonely MSC_TIMESTAMPs get emitted when
the touchpad works fine too. Is this expected behavior?


I would appreciate any pointer or feedback to help me work on it.

Andrea Monaco



[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux