Description of problem: The following messages're reported on journalctl several times while using the touchpad. There is no loss of functionality at all. I've seen this link, on arc, but no clue if it is the same issue i am facing https://bbs.archlinux.org/viewtopic.php?id=237288 Version-Release number of selected component (if applicable): How reproducible: For me, it happens every time. Steps to Reproduce: 1. let "journalctl --follow" on a terminal 2. use the touchpad 3. Actual results: Many error(?) messages being shown on the journalctl log while using the touchpad. Expected results: No error(?) messages concerning the usage of the touchpad Additional info: Log on journalctl: ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) ago 15 17:02:56 saka-pc kernel: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) Thanks in advance!!
Same here on kernel-4.17.17-200.fc28.x86_64. More than 20x per second.
I'm getting this error as well, using 4.19.5-200.fc28.x86_64. I recompiled the i2c_hid driver to output the invalid data, and ihid->inbuf appears to be all 0xff bytes: kernel: i2c_hid i2c-ELAN0501:01: input: ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: i2c_hid i2c-ELAN0501:01: i2c_hid_get_input: incomplete report (14/65535) libinput reports the device as: Device: ELAN0501:01 04F3:3060 Touchpad
i gave same error on fedora silverblue 29. [safarov@safarov-dell src]$ uname -a Linux safarov-dell.home 4.19.8-300.fc29.x86_64 #1 SMP Mon Dec 10 15:23:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I use Dell Inspiron 13 7000 Series 2-in-1 Laptop Dec 30 20:38:59 safarov-dell.home kernel: i2c_hid i2c-ELAN2097:00: i2c_hid_get_input: incomplete report (67/65535) Dec 30 20:38:59 safarov-dell.home kernel: i2c_hid i2c-ELAN2097:00: i2c_hid_get_input: incomplete report (67/65535) Dec 30 20:38:59 safarov-dell.home kernel: i2c_hid i2c-ELAN2097:00: i2c_hid_get_input: incomplete report (67/65535)
This messages related to device with ID 04F3:2502. This this related to touchscreen in my case. [root@safarov-dell .local]# xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ DELL07EB:00 06CB:7E7E Touchpad id=12 [slave pointer (2)] ⎜ ↳ ELAN2097:00 04F3:2502 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=19 [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)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ ELAN2097:00 04F3:2502 Pen id=14 [slave keyboard (3)] ↳ Intel Virtual Button driver id=15 [slave keyboard (3)] ↳ Intel HID events id=16 [slave keyboard (3)] ↳ Dell WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] This page may be usefull https://bbs.archlinux.org/viewtopic.php?id=233731
Issue is reproduces after PC sleep and resumed. Pressed power button two times. I have make some search in /sys subsystem [root@safarov-dell ~]# find /sys -name "*2097*" /sys/kernel/debug/regulator/reg-dummy-regulator-dummy/i2c-ELAN2097:00-vddl /sys/kernel/debug/regulator/reg-dummy-regulator-dummy/i2c-ELAN2097:00-vdd /sys/devices/platform/reg-dummy/regulator/regulator.0/i2c-ELAN2097:00-vddl /sys/devices/platform/reg-dummy/regulator/regulator.0/i2c-ELAN2097:00-vdd /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-8/i2c-ELAN2097:00 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:6c/ELAN2097:00 /sys/bus/acpi/devices/ELAN2097:00 /sys/bus/i2c/devices/i2c-ELAN2097:00 /sys/bus/i2c/drivers/i2c_hid/i2c-ELAN2097:00 And found that this device is not have ability to disconnect at run time. "delete_device" endpoint is not present. [root@safarov-dell i2c-ELAN2097:00]# cd /sys/bus/i2c/devices/i2c-ELAN2097:00 && ls -l total 0 drwxr-xr-x 6 root root 0 Dec 30 21:56 0018:04F3:2502.0006 lrwxrwxrwx 1 root root 0 Dec 30 21:56 driver -> ../../../../../../bus/i2c/drivers/i2c_hid lrwxrwxrwx 1 root root 0 Dec 30 21:56 firmware_node -> ../../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:6c/ELAN2097:00 -r--r--r-- 1 root root 4096 Dec 30 21:56 modalias -r--r--r-- 1 root root 4096 Dec 30 21:56 name drwxr-xr-x 2 root root 0 Dec 30 21:56 power lrwxrwxrwx 1 root root 0 Dec 30 21:56 subsystem -> ../../../../../../bus/i2c -rw-r--r-- 1 root root 4096 Dec 30 21:56 uevent [root@safarov-dell i2c-ELAN2097:00]# cat modalias acpi:ELAN2097:PNP0C50: [root@safarov-dell i2c-ELAN2097:00]# cat uevent DRIVER=i2c_hid MODALIAS=acpi:ELAN2097:PNP0C50:
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1622695
this is known issue in kernel module and root cause has not been determined (https://bugzilla.kernel.org/show_bug.cgi?id=201311) there is a known workaround by changing one single line in the kernel module source and recompile but fedora kernel managers seem to ignore the request to include the workaround in the kernel (https://bugzilla.redhat.com/show_bug.cgi?id=1662352#c3)
This seems to be fixed in kernel 5.1.0-rc2: https://bugzilla.kernel.org/show_bug.cgi?id=201311 It would be really great for fedora to backport the fix for fc29 !
I tested this RPMs and looks issue is fixed. ``` kernel-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm kernel-core-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm kernel-modules-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm ```
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
(In reply to Sergey Safarov from comment #9) > I tested this RPMs and looks issue is fixed. > ``` > kernel-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm > kernel-core-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm > kernel-modules-5.1.0-0.rc4.git0.1.fc31.x86_64.rpm > ``` Realy fixed on 5.1. Thank you fedora's dev team! That was so annoying to see my syslog floated with the same error! Great product ;) Best regards.