Bug 96308

Summary: tochpad jumping cursor
Product: Wayland Reporter: Daniele Denisi <daniele.denisi>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: blocker    
Priority: medium CC: benjamin.tissoires, daniele.denisi, peter.hutterer
Version: 1.2.x   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: evemu-record output
evemu-record output few seconds
dmesg
hid-record output
hid-record output from crazy state

Description Daniele Denisi 2016-06-01 15:13:28 UTC
hello everybody,
I am dealing with this issue:


Jun  1 16:24:17 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:17 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: (EE) kernel bug: Touch jump detected and discarded.
Jun  1 16:24:18 nb-daniele /usr/libexec/gdm-x-session[3830]: See https://wayland.freedesktop.org/libinput/doc/1.2.4/touchpad_jumping_cursor for detail
s




As suggested below you find all the infos about my enviroment:

libinput version : 1.2.4


 xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SYN1B7D:01 06CB:2991 Touchpad           	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ HD WebCam                               	id=10	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=12	[slave  keyboard (3)]
    ↳ Acer WMI hotkeys                        	id=13	[slave  keyboard (3)]



xinput list-props 11
Device 'SYN1B7D:01 06CB:2991 Touchpad':
	Device Enabled (136):	1
	Coordinate Transformation Matrix (138):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Tapping Enabled (272):	0
	libinput Tapping Enabled Default (273):	0
	libinput Tapping Drag Lock Enabled (274):	0
	libinput Tapping Drag Lock Enabled Default (275):	0
	libinput Accel Speed (276):	0.000000
	libinput Accel Speed Default (277):	0.000000
	libinput Natural Scrolling Enabled (278):	0
	libinput Natural Scrolling Enabled Default (279):	0
	libinput Send Events Modes Available (256):	1, 1
	libinput Send Events Mode Enabled (257):	0, 0
	libinput Send Events Mode Enabled Default (258):	0, 0
	libinput Left Handed Enabled (280):	0
	libinput Left Handed Enabled Default (281):	0
	libinput Scroll Methods Available (282):	1, 1, 0
	libinput Scroll Method Enabled (283):	1, 0, 0
	libinput Scroll Method Enabled Default (284):	1, 0, 0
	libinput Click Methods Available (285):	1, 1
	libinput Click Method Enabled (286):	1, 0
	libinput Click Method Enabled Default (287):	1, 0
	libinput Disable While Typing Enabled (288):	1
	libinput Disable While Typing Enabled Default (289):	1
	Device Node (259):	"/dev/input/event7"
	Device Product ID (260):	1739, 10641
	libinput Drag Lock Buttons (290):	<no items>
	libinput Horizonal Scroll Enabled (261):	1



netbook model : 

Acer E11

cat /sys/class/dmi/id/modalias
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:


Touchpad dimension:


1005mm  X 60mm



Btw Looking for the netbook specs, I found this link that suggest the cause of the problem is hardware: 

http://www.zachpoff.com/diy-resources/acer-laptop-touchpad-fix/



As soon as the touchpad goes crazy again , I will send you evemu-record outpu
Comment 1 Daniele Denisi 2016-06-01 15:23:28 UTC
Created attachment 124239 [details]
evemu-record output

evemu-record output in attachment
Comment 2 Peter Hutterer 2016-06-02 06:22:34 UTC
whoah, this really jumps all over the place. but it's a bit hard to debug because the recording contains almost 50000 lines, 2 minutes of events and it doesn't start from a neutral state. (also, clicking the link keeps crashing my browser). Please try to get a shorter recording, from a neutral state (i.e. finger off the touchpad), and only a single movement of a few seconds max. Thanks.
Comment 3 Daniele Denisi 2016-06-02 13:00:43 UTC
Created attachment 124267 [details]
evemu-record output few seconds

evemu-record output few seconds
Comment 4 Daniele Denisi 2016-06-02 13:11:33 UTC
Hello,
I have just sent you an attachement of a shorter event.

It's quite difficult to take a snapshot from a neutral state cause the passage from early state crazyness to deep crazyness is very fast.

If this log cannot help you I tought about a simple script that runs evemu-record, wait 2 seconds and then quit.

I call the script just "a" , and put it under /usr/local/bin so that when event happens , I can just do Alt+F2 --> "a" quickly to get more canches to record the events you need.


Thank you for your help,
Ciao
Daniele
Comment 5 Peter Hutterer 2016-06-03 00:11:58 UTC
wow, this is really messed up. Can you try a newer kernel please (grab one from F24). Looks familiar though, Benjamin, didn't we have a bug at some point where the ABS_MT_SLOT events where missing? this one looks exactly like that:

E: 0.030027 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +9ms
E: 0.038894 0003 0035 1088      # EV_ABS / ABS_MT_POSITION_X    1088
E: 0.038894 0003 0036 0162      # EV_ABS / ABS_MT_POSITION_Y    162
E: 0.038894 0003 0000 1088      # EV_ABS / ABS_X                1088
E: 0.038894 0003 0001 0162      # EV_ABS / ABS_Y                162
E: 0.038894 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +8ms
E: 0.047096 0003 0035 0384      # EV_ABS / ABS_MT_POSITION_X    384
E: 0.047096 0003 0036 0131      # EV_ABS / ABS_MT_POSITION_Y    131
E: 0.047096 0003 0000 0384      # EV_ABS / ABS_X                384
E: 0.047096 0003 0001 0131      # EV_ABS / ABS_Y                131
E: 0.047096 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +9ms
E: 0.054086 0003 0035 1223      # EV_ABS / ABS_MT_POSITION_X    1223
E: 0.054086 0003 0036 0405      # EV_ABS / ABS_MT_POSITION_Y    405
E: 0.054086 0003 0000 1223      # EV_ABS / ABS_X                1223
E: 0.054086 0003 0001 0405      # EV_ABS / ABS_Y                405
E: 0.054086 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +7ms
E: 0.062658 0003 0036 0449      # EV_ABS / ABS_MT_POSITION_Y    449
E: 0.062658 0003 0001 0449      # EV_ABS / ABS_Y                449
Comment 6 Benjamin Tissoires 2016-06-03 07:02:27 UTC
(In reply to Peter Hutterer from comment #5)
> wow, this is really messed up. Can you try a newer kernel please (grab one
> from F24). Looks familiar though, Benjamin, didn't we have a bug at some
> point where the ABS_MT_SLOT events where missing? this one looks exactly
> like that:

Hmm, not sure of which bug you are talking about, but this has been common in the early days of hid-multitouch when the protocol was still uncertain.

Daniele, please attach a dmesg and a hid-recorder output (package hid-replay in Fedora, run with "sudo hid-recorder"). In the hid recorder output, I'd like you to you to follow this procedure (whether the touchpad is working or not under X/wayland):
- single finger touch/release
- wait few secs
- one finger down, second finger down, first finger release, second finger release
- wait few secs
- then as put and move many fingers possible on the sensor (usually 10, but those small touchpads might be limited to 5 fingers, no need to call all your friends to stick too many fingers on the touchpad :-P )
Comment 7 Daniele Denisi 2016-06-05 22:18:41 UTC
Created attachment 124338 [details]
dmesg

dmesg
Comment 8 Daniele Denisi 2016-06-05 22:19:30 UTC
Created attachment 124339 [details]
hid-record output

hid-record output
Comment 9 Daniele Denisi 2016-06-05 22:20:04 UTC
Created attachment 124340 [details]
hid-record output from crazy state

hid-record output from crazy state
Comment 10 Daniele Denisi 2016-06-05 22:28:21 UTC
Peter,
let's try Benjamin suggestions before updating the kernel.

I have uploaded the output from dmesg and hid-recorer.

Firs hid-record output did not cause a crazy state, the second did.
Do not know if it is a mine suggestion but it seams that putting 5 finger on the touchpad calm the crazyness.


The cursor then is blocked for some seconds and after few seconds comes back to live again.



Ciao and thank you for your help Peter and Benjamin.



Daniele
Comment 11 Benjamin Tissoires 2016-06-06 08:37:20 UTC
Thanks for the logs. From the look of it, the first hid-recorder seems OK (though confidence is not set how I wanted it to be). On the second one, it really goes crazy:

  0.000000 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1175 | Y:    185 | Scan Time:  49461 | Contact Count:    1 | B1: 0 | # 
  0.009717 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1178 | Y:      0 | Scan Time:  49560 | Contact Count:    1 | B1: 0 | # 
  0.019703 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1223 | Y:    232 | Scan Time:  49655 | Contact Count:    1 | B1: 0 | # 
  0.028705 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1186 | Y:    145 | Scan Time:  49754 | Contact Count:    1 | B1: 0 | # 
  0.038611 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1178 | Y:    109 | Scan Time:  49844 | Contact Count:    1 | B1: 0 | # 
  0.048116 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1176 | Y:    215 | Scan Time:  49941 | Contact Count:    1 | B1: 0 | # 
  0.057634 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1223 | Y:      0 | Scan Time:  50036 | Contact Count:    1 | B1: 0 | # 
  0.066883 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1177 | Y:      0 | Scan Time:  50130 | Contact Count:    1 | B1: 0 | # 
  0.076872 ReportID: 3 / Confidence: 0 | Tip Switch: 1 | Contact Id:  1 | # | X:   1223 | Y:    268 | Scan Time:  50222 | Contact Count:    1 | B1: 0 | # 

Y gets reset to 0 quite a lot of times, while the Scan Time increments properly. I'd say you also have the same HW issue than the one in the link you shared (http://www.zachpoff.com/diy-resources/acer-laptop-touchpad-fix/) but I'll reach out to Synaptics to check with them if there is a software solution for this.
Comment 12 Benjamin Tissoires 2016-06-07 18:05:24 UTC
Synaptics' answer is that there is not much we can do on the software side. We "could" reset the touchpad when we detect this but this has a lot of issues (stuck fingers, takes time).

This has been fixed in the late production series (as seen in the link on the one you provided http://www.iq-tm.de/TP%20freeze.htm).

So basically, there is not much we can do unless you can crack open the laptop and add a proper ground to the touchpad :(
Comment 13 Daniele Denisi 2016-06-08 19:03:59 UTC
Thank you Benjamin,

I bought this netbook after my notebook has been stolen, just to continue working while deciding what to buy next. I will not risk to break it before I buy a new one.

As workaround I installed "touchpad indicator" gnome plugin instead. 
With a mouse plugged in , the touchpad is automatically disabled and I can continue to work.

Thank you again for the help.

I will let you know if I will do some hacks with the welder.


Ciao
Daniele

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.