Bug 101300

Summary: (EE) event7 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded.
Product: Wayland Reporter: Pacho Ramos <pachoramos1>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium CC: benjamin.tissoires, peter.hutterer
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: evemu-record
dmesg output
updated dmesg with psmouse tweak
updated dmesg with psmouse tweak
/proc/config.gz
/proc/config.gz
updated dmesg with psmouse tweak
updated dmesg with psmouse tweak
/proc/config.gz
acpidump

Description Pacho Ramos 2017-06-05 10:43:20 UTC
Created attachment 131707 [details]
evemu-record

I see this messages in logs:
jun 05 12:20:29 dell-2017 /usr/libexec/gdm-x-session[533]: (EE) event7  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded.
jun 05 12:20:29 dell-2017 /usr/libexec/gdm-x-session[533]: See https://wayland.freedesktop.org/libinput/doc/1.7.2/touchpad_jumping_cursor.html for details
jun 05 12:20:40 dell-2017 /usr/libexec/gdm-x-session[533]: (EE) event7  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded.
jun 05 12:20:40 dell-2017 /usr/libexec/gdm-x-session[533]: See https://wayland.freedesktop.org/libinput/doc/1.7.2/touchpad_jumping_cursor.html for details


# udevadm info /sys/class/input/event7 
P: /devices/platform/i8042/serio1/input/input8/event7
N: input/event7
E: DEVNAME=/dev/input/event7
E: DEVPATH=/devices/platform/i8042/serio1/input/input8/event7
E: ID_BUS=i8042
E: ID_INPUT=1
E: ID_INPUT_TOUCHPAD=1
E: ID_INPUT_TOUCHPAD_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=11/2/7/1a1:isa0060/serio1
E: LIBINPUT_MODEL_SYNAPTICS_SERIAL_TOUCHPAD=1
E: LIBINPUT_MODEL_TOUCHPAD_VISIBLE_MARKER=1
E: MAJOR=13
E: MINOR=71
E: SUBSYSTEM=input
E: USEC_INITIALIZED=3233340

Laptop: Inspiron 15 7000 Gaming

# cat /sys/class/dmi/id/modalias
dmi:bvnDellInc.:bvr01.00.05:bd03/01/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:

Dimensions of touchpad: 105x80mm (including buttons, 105x70 without them... buttons are "hidden" behind a cover including all the touchpad)
Comment 1 Peter Hutterer 2017-06-07 07:25:09 UTC
Bad news here, the jump isn't really detectable. so I think you'll have to live with the warnings in the log. 

In your evemu output, this one is the one that causes the jump:
  E: 3.805534 0003 0035 2627      # EV_ABS / ABS_MT_POSITION_X    2627
  E: 3.805534 0003 0036 4463      # EV_ABS / ABS_MT_POSITION_Y    4463
  E: 3.805534 0003 003a 0066      # EV_ABS / ABS_MT_PRESSURE      66
  E: 3.805534 0003 0000 2627      # EV_ABS / ABS_X                2627
  E: 3.805534 0003 0001 4463      # EV_ABS / ABS_Y                4463
  E: 3.805534 0003 0018 0066      # EV_ABS / ABS_PRESSURE         66
  E: 3.805534 0000 0000 0000      # ------------ SYN_REPORT (0) ---------- +14ms

This is 3 events after one at 4330/2314. The only possible indication about the jump is the presence of three pressure-only events, but I'm not sure that's reliable enough. Unless there are other side-effects, living with the warning in the log is the simplest solution here.

Please do attach the output of the touchpad-edge-detector though, this device doesn't have axis ranges set so we need to override it.
Comment 2 Pacho Ramos 2017-06-07 07:46:12 UTC
Sure :)
# touchpad-edge-detector 105x70 /dev/input/event7 
Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event7
Move one finger around the touchpad to detect the actual edges
Kernel says:	x [1278..5664], y [1206..4648]
Touchpad sends:	x [1285..5665], y [1207..4649] /^C[F

Touchpad has no resolution, size unknown
User-specified touchpad size: 105x70mm
Calculated ranges: 4380/3442

Suggested udev rule:
# <Laptop model description goes here>
evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnDellInc.:bvr01.00.05:bd03/01/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:*
 EVDEV_ABS_00=1285:5665:42
 EVDEV_ABS_01=1207:4649:49
 EVDEV_ABS_35=1285:5665:42
 EVDEV_ABS_36=1207:4649:49
Comment 3 Peter Hutterer 2017-06-07 09:25:05 UTC
thanks, I'll get that into systemd upstream. Please also attach your dmesg so benjamin can have a look why this is needed in the first place
Comment 4 Pacho Ramos 2017-06-07 09:39:15 UTC
Created attachment 131765 [details]
dmesg output

Attached
Comment 5 Benjamin Tissoires 2017-06-07 12:41:07 UTC
(In reply to Pacho Ramos from comment #4)
> Created attachment 131765 [details]
> dmesg output
> 
> Attached

Thanks. However, I do not see what could be wrong besides the firmware not providing the correct resolution :(

Given that you are on gentoo, could you give a shot at a kernel v4.12-rcX and boot it with "psmouse.synaptics_intertouch=1" appended to the kernel boot line to see if your device works with RMI4 over SMBus, and if this solves the issue.
Comment 6 Pacho Ramos 2017-06-07 14:50:57 UTC
Are you sure it's the dmesg output the want you need? I mean, the errors are shown in "journalctl -e" output (coming from X I think)

I can try, of course :)
Comment 7 Benjamin Tissoires 2017-06-07 14:56:29 UTC
(In reply to Pacho Ramos from comment #6)
> Are you sure it's the dmesg output the want you need? I mean, the errors are
> shown in "journalctl -e" output (coming from X I think)

Yes, I am interested in the dmesg. We know why there are errors in X or Wayland: the kernel sends garbage (or at least an unconfigured device), so I am interested in what the kernel exports. And for that, dmesg is the place to look for errors or debug information.

> I can try, of course :)

Thanks!
Comment 8 Pacho Ramos 2017-06-07 15:08:11 UTC
Created attachment 131778 [details]
updated dmesg with psmouse tweak

This is the updated dmesg output... for now I don't see any errors related with the jumping in logs :/
Comment 9 Benjamin Tissoires 2017-06-07 15:14:54 UTC
Please also enable MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB in your .config (and probably any RMI4_* option).
Comment 10 Pacho Ramos 2017-06-08 08:43:09 UTC
Created attachment 131791 [details]
updated dmesg with psmouse tweak

this is the updated one
Comment 11 Pacho Ramos 2017-06-08 08:44:05 UTC
Created attachment 131792 [details]
/proc/config.gz
Comment 12 Benjamin Tissoires 2017-06-08 09:07:47 UTC
I was confused why the touchpad doesn't appear on the SMBus.

And then I realized that you have CONFIG_I2C_HID not set. Please turn this on, and the touchpad should be handled by HID now.

Then, you should at least enable CONFIG_HID_MULTITOUCH, and CONFIG_HID_RMI for this touchpad to be handled properly.

Then, you should probably review trhe config of most HID modules (especially CONFIG_HID_LOGITECH_DJ and CONFIG_HID_LOGITECH_HIDPP) if you ever want to plug an input device that we support in a special way in the kernel. I suspect you might also be interested in CONFIG_HID_SENSOR_HUB in case your laptop exports some accelerometer/light sensor.
Comment 13 Pacho Ramos 2017-06-08 09:31:47 UTC
Created attachment 131793 [details]
/proc/config.gz

updated config
Comment 14 Pacho Ramos 2017-06-08 09:32:16 UTC
Created attachment 131794 [details]
updated dmesg with psmouse tweak

updated one
Comment 15 Benjamin Tissoires 2017-06-08 09:54:10 UTC
...and you probably also need CONFIG_I2C_DESIGNWARE_PLATFORM, CONFIG_I2C_DESIGNWARE_PCI to have a driver for the I2C controller that can handle the touchpad.
Comment 16 Pacho Ramos 2017-06-08 11:58:39 UTC
Created attachment 131799 [details]
updated dmesg with psmouse tweak
Comment 17 Pacho Ramos 2017-06-08 11:58:55 UTC
Created attachment 131800 [details]
/proc/config.gz
Comment 18 Benjamin Tissoires 2017-06-09 07:46:52 UTC
I feel a littlbe bit like playing whack a mole here.

Could you just to be sure download a livecd of Fedora 25 and see if your touchpad behave the same?
If it is handled by hid-multitouch, you probably want to compare the loaded modules from the livecd to yours under gentoo.

Also, just to be sure that it's a HID touchpad, could you attach the output of acpidump (as root)?
Comment 19 Pacho Ramos 2017-06-12 10:44:51 UTC
Anyway, since running kernel 4.12-rc4 with this boot options I don't see the "jump" error in logs :/
Comment 20 Pacho Ramos 2017-06-12 10:45:10 UTC
Created attachment 131888 [details]
acpidump
Comment 21 Peter Hutterer 2017-06-30 01:10:50 UTC
(In reply to Pacho Ramos from comment #19)
> Anyway, since running kernel 4.12-rc4 with this boot options I don't see the
> "jump" error in logs :/

that's a good sign, unless you noticed a pointer jump?
Comment 22 Pacho Ramos 2017-07-03 08:04:00 UTC
But without that boot options, I still see the messages... anyway, the messages don't show any issues with a normal usage, I only reported because I saw the errors in journalctl output and wanted to let you know :/
Comment 23 Peter Hutterer 2017-08-18 02:51:42 UTC
for the 4.12 kernel, the boot option is the default for your device. so once you update to 4.12, everything should work fine :)
Comment 24 Pacho Ramos 2017-08-30 13:20:40 UTC
OK, thanks a lot :)

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.