touchpad not working after resume on kernel 4.13

[Mikolaj Kucharski]

I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel:

$ uname -rv
4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017

and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume:

PM: Device i2c-SYNA3105:00 failed to resume async: error -11

and I can find other people reporting similar issue on other distros:

https://bugzilla.redhat.com/show_bug.cgi?id=1431375
https://bugzilla.kernel.org/show_bug.cgi?id=195949
https://bugzilla.redhat.com/show_bug.cgi?id=1442699

like in those other bug reports I can workaround the problem by:

rmmod i2c-hid
modprobe i2c-hid

in systemd-suspend.service(8) post scripts.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mkucharski 1367 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 15 22:49:38 2017
HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857
InstallationDate: Installed on 2017-10-06 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink)
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Timi TM1607
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2017
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: XMAKB200P0100
dmi.board.asset.tag: Any
dmi.board.name: TM1607
dmi.board.vendor: Timi
dmi.board.version: MP
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion:
dmi.product.family: Timibook
dmi.product.name: TM1607
dmi.sys.vendor: Timi

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Mikolaj Kucharski (mikolaj-kucharski)]

a bit more lines from syslog when issue happens:

Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed
Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed
Oct 08 18:04:27 mi-air kernel: rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask.
Oct 08 18:04:27 mi-air kernel: dpm_run_callback(): i2c_hid_resume+0x0/0x120 [i2c_hid] returns -11
Oct 08 18:04:27 mi-air kernel: PM: Device i2c-SYNA3105:00 failed to resume async: error -11

[Mikolaj Kucharski (mikolaj-kucharski)]

Previous dmesgs are with 4.13.0-12-generic, as the same problem was present with 4.13.0-12-generic, 4.13.0-15-generic and now is present with 4.13.0-16-generic.

[Mikolaj Kucharski (mikolaj-kucharski)]

errors from kernel after resume (same as one of my previous comments)

[Mikolaj Kucharski (mikolaj-kucharski)]

Per external references to RedHat's bugzilla solution for the problem should be:

https://patchwork.kernel.org/patch/9858267/

however I didn't had a chance to test it yet on latest Ubuntu 17.10 kernel.

[Joseph Salisbury (jsalisbury)]

To see if this bug is fixed upstream, please test the latest upstream kernel. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 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.14-rc5

[Mikolaj Kucharski (mikolaj-kucharski)]

I did following:

dpkg -i \
 linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \
 linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb \
 linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb

and rebooted the system to new kernel. Yes I can confirm that kernel 4.14.0-041400rc5-generic fixes the problem for me. With this new kernel however Wi-Fi doesn't work, but that's another issue. Wi-Fi works with 4.13.0-16-generic and previous kernels from Ubuntu 17.10

[Mikolaj Kucharski (mikolaj-kucharski)]

Let me know do you need anything else. Will be possible to backport fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works after resume on default Artful Aardvark install?

[Joseph Salisbury (jsalisbury)]

Could you also give the latest upstream stable 3.13 kernel a try? It is available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.7/

[Mikolaj Kucharski (mikolaj-kucharski)]

I did the same with:

$ uname -rv
4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017

and also this kernel works for me and touchpad works after resume. What is also nice, Wi-Fi works after resume.

[Alberto Pianon (alberto-o)]

4.13.7-041307-generic fixes the issue also for me (Lenovo Yoga 3 11, fresh Ubuntu 17.10 install)

[Mikolaj Kucharski (mikolaj-kucharski)]

This problem is fixed with latest kernel update on Ubuntu 17.10:

# uname -rv
4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017

[Nicolai P (nicolaip)]

I can confirm that it works again on the latest kernel version.

[Jarad Downing (jaraddowning)]

This bug has started affecting me on 4.15.0-20-generic #21-Ubuntu. Not sure if it's been reported on that release, not sure how to report it on the correct release.

[William Linna (william-linna)]

I too am affected now. After suspend+resume, my touchpad isn't found. Rebooting doesn't help: I really have to turn the machine off and on again.

I can attach mouse, and then if I try to open touchpad settings in Input Devices settings (I use Kubuntu), it says that Touchpad isn't found, and xinput doesn't show it either.

- Fujitsu E556 laptop
- 4.15.0-20-generic #21-Ubuntu

I still have Ubuntu 16.04 on one SSD with the kernel 4.4.0-119-generic, and the issue doesn't appear there. I think the issue didn't appear on Kubuntu 17.04 either. I didn't try 17.10.

The workaround mentioned in the original post didn't work for me. When I ran
sudo modprobe i2c-hid, I got this message:

rmmod: ERROR: Module i2c_hid is not currently loaded

The command
sudo modprobe i2c-hid

completed, but the touchpad didn't start working.

[William Linna (william-linna)]

Here's dmesg after resume

[Joseph Salisbury (jsalisbury)]

Can those affected by this bug in Bionic open a new bug?

[Mikolaj Kucharski (mikolaj-kucharski)]

I don't think this is the same bug and new bug report should be opened. I've reported problem here back in October 2017 with my laptop and problem was solved with kernel upgrade on Artful. Recently I upgraded same laptop to Bionic and I am not affected by the bug.

[swissz (zsarosi)]

Hi

I wrote this text to #1722379, but I think it worth to mention it here as well.

Recently, after some updates - unfortunatelly I don't know exactly which updates, but in the last month - I also have the same problem.
The workaround above with the # rmmod i2c_hid && modprobe i2c_hid works, but I also have a different workaround: if I switch to a virtual terminal with CTRL+ALT+1 then back to the GUI Terminal CTRL+ALT+7 the clickpad works again.
I hope this new aspect of switching virtual terminals back and forth helps to understand/debug the issue better.