Ubuntu
linux package

i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

Bug #1798363 reported by blurhy
72
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
............

Lots of these things

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: blurhy 2908 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 17 20:07:13 2018
InstallationDate: Installed on 2018-10-10 (6 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc.
 Bus 001 Device 003: ID 13d3:5666 IMC Networks
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. FX503VD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic N/A
 linux-firmware 1.175
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX503VD.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX503VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: FX
dmi.product.name: FX503VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
blurhy (blurhy) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

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.19 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.19-rc8

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
importance: Undecided → Medium
blurhy (blurhy)
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
In , caravena (caravena-linux-kernel-bugs) wrote :

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1798363

"Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)"

Best regards,
--
Cristian Aravena Romero (caravena)

Revision history for this message
Dmitry Diskin (diskin) wrote :

Is it a duplicate of 1778087?

Revision history for this message
blurhy (blurhy) wrote :

Maybe . But there is a bit difference,my touchpad always works after updated to 18.10

Revision history for this message
Luke Williams (wililupy) wrote :

This has been an issue ever since I have used this laptop with any distribution of Linux. Up until 18.10 with touchpad would be non-functional. It would jump all over the screen and would basicaly be unusable with the laptop. Since 18.10. and kernel 4.17.4 the touchpad works as far as no longer jumping around the screen, but as soon as you touch the touchpad with all 5 fingers, it crashes and can no longer use the touchpad. Also, after about 10 minutes of use, the touchpad locks up and the only way to get it back is to either reboot the laptop or unload the kmods for the elan device and reload them and then you can use the touchpad for about 20 minutes again.
I created a cron job that does this every 5 minutes so that I can use my touchpad with out worry or I just use an external mouse.

The troublesome thing about this is that this laptop has been around for over a year, and with Windows, there are no issues, and with the UEFI BIOS, the mouse works with no issues. Just Linux.

Revision history for this message
blurhy (blurhy) wrote :

Touchpad still doesn't work randomly.

Bug Watch Updater (bug-watch-updater)
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , kdavrn (kdavrn-linux-kernel-bugs) wrote :

The same error

5.0.0-050000rc5-generic
Ubuntu 18.10
ZenBook 13 UX331UAL

dmesg | grep -i i2c_hid
[ 0.984305] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 0.984317] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[ 0.984318] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator
[ 306.130804] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
[ 3257.587678] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
[ 3401.698609] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

Revision history for this message
In , bugzilla (bugzilla-linux-kernel-bugs) wrote :

Here the same errors and erraric behaviour. Five finger or palm touch hangs touchpad. Sometimes timeout messaged are generated and sometimes it just 'hangs' :

i2c_designware i2c_designware.0: controller timed out
i2c_designware i2c_designware.0: timeout in disabling adapter
i2c_designware i2c_designware.0: timeout waiting for bus ready

Sporadically the 'incomplete report' messages are generated:

i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

This is on Fedora 29 with kernel:

Linux deathstar 4.20.8-200.fc29.x86_64 #1 SMP Wed Feb 13 13:08:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
In , linesma (linesma-linux-kernel-bugs) wrote :

This bug is present on an Asus FX504G. It does not matter if one is running Synaptics or libinput. The error message will eventually cause the touchpad to stop operating completely. It will start working again after a period of time. However, to have it operate again immediately, I have to type: rmmod hid-multitouch && modprobe hid-multitouch in a root terminal.

This is on Manjaro 18.03 running Gnome 3.30.2 with kernel:

Linus FX504DG 4.20.11-1-MANJARO #1 SMP PREEMPT Wed Feb 20 23:19:36 UTC 2019 x86_64 GNU/LINUX

cat /proc/bus/input/devices

I: Bus=0018 Vendor=04f3 Product=3090 Version=0100
N: Name="ELAN1200:00 04F3:3090 Touchpad"
P: Phys=i2c-ELAN1200:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input17
U: Uniq=
H: Handlers=event13 mouse1
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

dmesg | grep -i i2c-ELAN
[ 3.391117] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 3.391136] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[ 3.391139] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator
[ 3.603805] input: ELAN1200:00 04F3:3090 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input13
[ 3.603874] input: ELAN1200:00 04F3:3090 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input14
[ 3.603943] hid-generic 0018:04F3:3090.0004: input,hidraw3: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3090] on i2c-ELAN1200:00
[ 3.734501] input: ELAN1200:00 04F3:3090 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input17
[ 3.734614] hid-multitouch 0018:04F3:3090.0004: input,hidraw3: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3090] on i2c-ELAN1200:00
[ 56.806547] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

Revision history for this message
In , ryan.reich (ryan.reich-linux-kernel-bugs) wrote :

I also have this exact problem. The frozen pointer can actually be revived with `xinput --disable 13; xinput --enable 13` (substitute the correct number from the `xinput` listing). A palm or 5-finger touch will not respond to this, however, and can only be fixed by suspending and resuming (which, I assume, has the same effect as the `modprobe` cycle, but I have compiled the driver in). Occasionally, the entire keyboard freezes and I need to reboot.

Revision history for this message
In , linesma (linesma-linux-kernel-bugs) wrote :

(In reply to Ryan Reich from comment #4)
> I also have this exact problem. The frozen pointer can actually be revived
> with `xinput --disable 13; xinput --enable 13` (substitute the correct
> number from the `xinput` listing). A palm or 5-finger touch will not
> respond to this, however, and can only be fixed by suspending and resuming
> (which, I assume, has the same effect as the `modprobe` cycle, but I have
> compiled the driver in). Occasionally, the entire keyboard freezes and I
> need to reboot.

I have not tried that. I also have all the multitouch features turned off. The difference between my "work around" and yours is that mine resets the whole driver not just the touchpad. It seems to be an issue with the architecture related to the Coffee Lake series of Intel processors.

Revision history for this message
In , voronov.semyon (voronov.semyon-linux-kernel-bugs) wrote :
Download full text (3.6 KiB)

I also have this issue. The pointer becomes frozen about 1-2 sec, at this time, it can move, but no actions work. My laptop: Xiaomi Mi Notebook Pro rev.2

any touch on the touchpad generates a bunch of errors:

i2c_hid i2c-ETD2303:00: i2c_hid_get_input: incomplete report (14/65535)

This issue is relevant for kernel version 4.20.13. OS: Arch linux.

xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETD2303:00 04F3:3083 Touchpad id=11 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=14 [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)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ XiaoMi USB 2.0 Webcam: XiaoMi U id=10 [slave keyboard (3)]
    ↳ Intel HID events id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]

Device: ETD2303:00 04F3:3083 Touchpad
Kernel: /dev/input/event6
Group: 6
Seat: seat0, default
Size: 125x78mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: none
Rotation: n/a

Device: ETPS/2 Elantech Touchpad
Kernel: /dev/input/event9
Group: 10
Seat: seat0, default
Size: 125x81mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: none
Rotation: n/a

journalctl -b | grep i2c | grep -v 'incomplete report'

мар 05 01:25:42 KarmicMiBook kernel: i2c_hid i2c-ETD2303:00: i2c-ETD2303:00 supply vdd not found, using dummy regulator
мар 05 01:25:42 KarmicMiBook kernel: i2c_hid i2c-ETD2303:00: Linked as a consumer to regulator.0
мар 05 01:25:42 KarmicMiBook kernel: i2c_hid i2c-ETD2303:00: i2c-ETD2303:00 supply vddl not found, using dummy regulator
мар 05 01:25:42 KarmicMiBook kernel: input: ETD2303:00 04F3:3083 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ETD2303:00/0018:04F3:3083.0001/input/input8
мар 05 01:25:42 KarmicMiBook kernel: input: ETD2303:00 04F3:3083 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ETD2303:00/0018:04F3:3083.0001/input/input10...

Read more...

Revision history for this message
In , smartways897 (smartways897-linux-kernel-bugs) wrote :

Hello, I also have the same issue on my Asus GL503GE. This touchpad actually worked on kernel 4.20.16, but after I updated the kernel to 5.0.3, the touchpad didn't respond at all. So here is my dmesg log :

[ 5.648605] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 5.651130] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[ 5.653404] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator
[ 5.883577] input: ELAN1200:00 04F3:3090 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-7/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input25
[ 5.884831] input: ELAN1200:00 04F3:3090 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-7/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input26
[ 5.886132] hid-generic 0018:04F3:3090.0004: input,hidraw3: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3090] on i2c-ELAN1200:00
[ 5.939805] input: ELAN1200:00 04F3:3090 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-7/i2c-ELAN1200:00/0018:04F3:3090.0004/input/input28
[ 5.940973] hid-multitouch 0018:04F3:3090.0004: input,hidraw3: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3090] on i2c-ELAN1200:00
[ 19.557227] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/255)

And here is my xinput log
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver Mouse id=14 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver Consumer Control id=15 [slave pointer (2)]
⎜ ↳ Asus Keyboard id=17 [slave pointer (2)]
⎜ ↳ ELAN1200:00 04F3:3090 Touchpad id=18 [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)]
    ↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ Sleep Button id=11 [slave keyboard (3)]
    ↳ Logitech USB Receiver id=12 [slave keyboard (3)]
    ↳ Logitech USB Receiver System Control id=13 [slave keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=16 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=19 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=20 [slave keyboard (3)]
    ↳ Logitech USB Receiver Consumer Control id=21 [slave keyboard (3)]
    ↳ Asus Keyboard id=22 [slave keyboard (3)]

My OS is Fedora 29 using latest Linux kernel 5.0.3-200.fc29.x86_64

Kaiqiang Li (kaiqiang1)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
In , bugzilla (bugzilla-linux-kernel-bugs) wrote :

Small update for a quick workaround on hanging touchpad:

Instead of unloading/loading kernel modules a quicker way is to go to a terminal screen and back to X11:

- Press <ctrl><alt><f2> to enter terminal mode
- Press <alt><f1> to go back to X11

Note that the F-keys can differ, this works on Fedora 29 with Cinnamon and kernel 5.0.3-200

Revision history for this message
Vladimir Yerilov (openmindead) wrote :

>> status: Confirmed → Fix Released
Any hint where can I find relevant patch?

Revision history for this message
You-Sheng Yang (vicamo) wrote :

This has been fixed by upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1475af255e18f35dc46f8a7acc18354c73d45149 , which has been backported to Cosmic 4.18.0-16.17, Bionic 4.15.0-46.47, Disco 4.19.0-13.14.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
In , Ed Romana (erom) wrote :

For my Assus Q304uak laptop, both the touchpad and the keyboard misbehave. My default laptop Linux kernel options are organized in 6 families form 4.4 through 4.15.

After some time, for all kernels in the ranges 4.8, 4.10, 4.11, 4.13 the keyboard will freeze.

My first, successful boot and keyboard stable kernel version is 4.4.0-70-generic, upstart. Other kernels tested in 4.4 also have a stable keyboard

The touchpad misbehaves for all kernels tested.

A suspend–resume cycle restores the touch pad for short period of time, a few minutes. Less reliably the key press sequences of ctrl-alt-f2 and ctrl-left-alt-f7 also restores the touchpad for a few minutes if at all.

Fortunately the USB mouse ports function normally for all kernels used.

Revision history for this message
In , Ed Romana (erom) wrote :

I also get
dmesg | grep -i i2c_hid
[ 847.000642] i2c_hid i2c-ELAN1301:00: i2c_hid_get_input: incomplete report (16/16466)
[ 1869.470878] i2c_hid i2c-ELAN1301:00: i2c_hid_get_input: incomplete report (16/16466)

Revision history for this message
Guillaume (xplodwild) wrote :

This is still happening on recent kernels, and affecting newer machines (Razer Blade 15 mid-2021 model). The trackpad works mostly fine after boot, but after sleep and resume, the trackpad goes funky (moving the cursor leads to random clicks, etc) and the kernel log is spamming the same "incomplete report" message:

Sep 12 08:57:09 mana kernel: [ 571.107703] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
Sep 12 08:57:09 mana kernel: [ 571.108429] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
Sep 12 08:57:09 mana kernel: [ 571.109164] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
Sep 12 08:57:09 mana kernel: [ 571.109889] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
Sep 12 08:57:09 mana kernel: [ 571.110613] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
Sep 12 08:57:09 mana kernel: [ 571.111337] i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)

It works fine again after a full reboot. I get no issues on Windows with the same hardware, fwiw.

Running kernel 5.11.0-34 on Ubuntu 21.04.

Revision history for this message
Alex Thiel (apockill) wrote :

I also have this issue on my Razer Blade 15 (2021) running Ubuntu 20.04 5.11.0-37

Are there any workarounds?

Revision history for this message
Paul Decoursey (optimuspaul) wrote :

I am seeing this as well on my Razer Blade 15 Advanced (2021). Only happens after it wakes from sleep.

Revision history for this message
Paul Decoursey (optimuspaul) wrote :

Finding now that it doesn't just happen after sleep, but also occurs when a restart is initiated.

I'm running kernel 5.13.0-7620 POP!_OS 21.04

Revision history for this message
pg (mango1) wrote :

Chiming in that I also experience this issue on my Razer Blade 17 (2021) running ElementaryOS 6 (5.11.0-38-generic).

Revision history for this message
Jonas Konrath (nighmared) wrote :

Same issue on Acer Swift 5 (2019). Would love to see a fix or workaround..
(Had it on Pop_OS as well as normal Ubuntu (5.11 & 5.10). Now same on fedora with 5.14.16-301 )

Don't think this is a duplicate, because 1813733 only deals with excessive log messages and not unusable touchpads

Revision history for this message
In , JC Reus (suenteus) wrote (last edit ):

I'm still seeing this problem happening on a Razer Blade 15 Advanced (mid-2021). Running kubuntu 20.04 LTS with kernel 5.11
The issue only happens after a resume from suspend (both on laptop lid close and on suspend from the command line using `sudo pm-suspend`

Upon wake, the mouse is jerky, clicking on things, and becomes increasingly unresponsive. The terminal (dmesg) is constantly writing:

```
i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)
```

None of the workarounds I have seen seem to be able to restore the trackpad to working order. Such as..

```
sudo rmmod i2c_hid hid_multitouch && sudo modprobe i2c_hid hid_multitouch
```

and

```
xinput --disable 19 && xinput --enable 19
```

Only a hard shutdown and a restart seem to fix things.

Revision history for this message
fez (fezed) wrote :

Same problem on pop os with Razer Blade 15 Advanced (mid-2021)

i2c_hid i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/65535)

Please fix this someone I cant use trackpad after waking up from sleep

Revision history for this message
In , fez (fezed) wrote :

Exact same here

Revision history for this message
dimsua (dimsua) wrote :

The same error

Xubuntu Linux 20.04.3
Linux 5.11.0-40-generic on x86_64
AsusPRO BR1100CKA-GJ0382 (90NX03B1-M05180)

i2c_hid i2c-ASUE1201:00: i2c_hid_get_input: incomplete report (16/65535)

Revision history for this message
fez (fezed) wrote :

Rmmod and modprone i2c_hid doesn't work. I can't figure out what's causing this problem I tried all the lastest Linux kernels and still same issue

Revision history for this message
abovemind (abovemind) wrote (last edit ):

I am also getting a similar issue on a Razer Blade 15 Advanced (mid-2021)

    i2c_hid_acpi i2c-ELAN0406:00: i2c_hid_get_input: incomplete report (14/60416)

The only fix that seems to work is a reboot. rmmod and modprobe i2c_hid and i2c_hid_acpi don't seem to fix the issue. The only workaround I have found is to disable sleep, and to just use hibernate.

The issue has occurred with all kernels I have tried between 5.13.0 and 5.14.21.

Revision history for this message
mirh (mirh) wrote (last edit ):

"Acpi_osi=" to the kernel command line is supposed to make a difference on razer laptops.
https://old.reddit.com/r/pop_os/comments/pkeh4r/i2c_hid_get_input_flooding/

But first try 5.15. It should have fixed a very long regression chain in ELAN i2c touchpads.

Revision history for this message
Loïc BEFVE (loicbefve) wrote :

Same here on Razer Blade 15 Advanced Model (mid-2021). Trackpad isn't working after suspend. My kernel is 5.15.0-2-amd64.

Revision history for this message
Andy Barry (abarry-gmail) wrote :

Same here on Razer Blade 15 Advanced (2022). I tried acpi_osi= in the grub line and that results in the trackpad not working at all upon reboot.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.