psmouse: after sleep/suspend thinkpad touchpad not functional

Bug #1788928 reported by Joshua Powers
This bug report is a duplicate of:  Bug #1786574: remove i2c-i801 from blacklist. Edit Remove
70
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned
Bionic
Confirmed
Medium
Unassigned

Bug Description

Summary:
The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly.

Expected Behavior:
After sleep/suspend scroll works correctly.

Actual Behavior:
Unable to scroll or correctly click on a window and move it without reloading the driver

Steps to reproduce:
1. Install Bionic on Thinkpad X1 (4.15.0-32-generic)
2. Open something to scroll (e.g. browser, terminal, etc.)
3. Close lid
4. Re-open lid once sleeping/suspended
5. Try to scroll and note that it does not work

Workaround:
Run the following after re-opening the lid
$ sudo modprobe psmouse -r; sudo modprobe psmouse

dmesg on reload:
[12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758]
[12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..]
[12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access
[12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet
[12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x10000, board id: 3072, fw id: 1795685
[12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24
[12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: powersj 2506 F.... pulseaudio
 /dev/snd/controlC0: powersj 2506 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
InstallationDate: Installed on 2018-02-19 (185 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
Lsusb:
 Bus 001 Device 002: ID 8087:8001 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20BSCTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: bionic
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET42W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 3rd
dmi.product.name: 20BSCTO1WW
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO

Revision history for this message
Joshua Powers (powersj) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
Joshua Powers (powersj) wrote : CRDA.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : IwConfig.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : Lspci.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : ProcModules.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : PulseList.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : UdevDb.txt

apport information

Revision history for this message
Joshua Powers (powersj) wrote : WifiSyslog.txt

apport information

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
Joseph Salisbury (jsalisbury) 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.18 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.18.3

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Bionic):
importance: Undecided → Medium
status: New → Confirmed
tags: added: kernel-da-key
Revision history for this message
Server Team CI bot (server-team-bot) wrote :

Added kernel-bug-exists-upstream as this occurs on 4.18.3-041803-generic.

> Did this issue start happening after an update/upgrade?
No

> Was there a prior kernel version where you were not having this particular problem?
On Bionic, I think I have always had this issue

tags: added: kernel-bug-exists-upstream
Revision history for this message
Anthony Wong (anthonywong) wrote :

Do you have "blacklist i2c_i801" in /etc/modprobe.d/blacklist.conf? If so could you remove the line, reboot and test again? Post dmesg if anything is not working well.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try kernel parameter "psmouse.synaptics_intertouch=0".

Revision history for this message
Joshua Powers (powersj) wrote :

> Do you have "blacklist i2c_i801" in /etc/modprobe.d/blacklist.conf?

Yes it was there. I commented it out, rebooted, and tried the test again. Afterwards there were no issues \o/ I repeated the test again and it continued to work as expected.

> Please try kernel parameter "psmouse.synaptics_intertouch=0".

I re-blacklisted the i2c_i801 module above, added the parameter to /etc/default/grub, and regenerated my grub. After reboot I ran the test again and there were no issues. I again repeated the test and it continued to work as expected.

Revision history for this message
Anthony Wong (anthonywong) wrote :

Thanks for the testing! We have another bug to remove i2c_i801 from blacklist.conf, so I will set this bug as a duplicate.

Revision history for this message
bill (bill-zannoni) wrote :

I've recently installed Ubuntu 18.04.01 on a Lenovo S540 laptop (full disk installation).
I have the kernel 4.15.0-43-generic and I had the same problem.
In my /etc/modprobe.d/blacklist.conf there was not module "i2c_i801" blacklisted, but still the touchpad would be inactive after a wake-up from suspension and it would come back after a restart.

Adding the parameter "psmouse.synaptics_intertouch=0" to grub solved the issue.

Revision history for this message
Mathias (gnillev) wrote :

Commenting to help others: I'm on Ubuntu 18.10 on a Lenovo L540 laptop and had the same problem.
I didn't have i2c_i801 in my blacklist either, but still the touchpad would be unresponsive after suspend (so not a duplicate of #1786574).

Adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in /etc/default/grub seems to have solved it for me as well.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
StefanF (stefan) wrote :

I had a similar issue on my HP Omen Laptop with Debian 20. After resume from long suspend (several hours), my touchpad always generated random button events even while not touched.

I have exactly the same situation as Mathias wrote in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/comments/22

I didn't have i2c_i801 in my blacklist, but adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in /etc/default/grub solved the problem.

Revision history for this message
StefanF (stefan) wrote :

One more info: When the problem occured, I always had to cold restart my laptop (power off/on). A warm reboot did never help. Also reloading the psmouse module did never help.

Revision history for this message
Youssoufou YABRE (yyabre) wrote :

I had the same problem with ubuntu 20.04 daily build on
Thinkpad T440s .

adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in /etc/default/grub solved the problem.

Revision history for this message
Ketil Malde (ketil-ii) wrote :

Chiming in. Lenovo X1C gen 7, with NFC symbol, running Ubuntu 19.10 (5.3.0-24-generic), and trackpad not working after wakeup from suspend (not sure which level, I just close the lid, notice leds slowly blinking, then open it again). Nothing about i2c in any /etc/modprobe.d/* file.

Only caveat: running 1.20 system firmware (20QD00L1MX System Firmware) since the latest gives me an unreliable external display when using USB-C/Thunderbolt.

Revision history for this message
StefanF (stefan) wrote :

From Kai-Heng Feng (kaihengfeng):
> Please try kernel parameter "psmouse.synaptics_intertouch=0".

Thank you so much, this solved the problem on my HP Omen 15-ax005ng Laptop as well.

Revision history for this message
Victorious (makyil-9) wrote :

From Kai-Heng Feng (kaihengfeng):
> Please try kernel parameter "psmouse.synaptics_intertouch=0".

Thank you. This solved my wake up problem on Lenovo Helix Tablet.

Revision history for this message
... (fabss) wrote :

I face the same issue with a lenovo thinkpad t420. After suspending the left mouse button does not work. Everything else works fine.

I tried your suggestions with uncommenting i2c_i801 and adding "psmouse.synaptics_intertouch=0" to grub. First I tried uncommenting; this did not work. Then I added "psmouse.." to grub and keep i2c_i801 uncommented; this did not work. After that I tried only addind "psmouse.." to grub which also did not work. I also tried to delete and add psmouse and i2c_i801 from kernel with modprobe. Also no changes.

Another strange thing is, if I run "xinput list" and choose the id of "SynPS/2 Synaptics TouchPad" and run "xinput --test 11" I get the following result after pressing left button (1) first and then right button (3):

button press 1
button release 1
button press 3
button release 3

So it seems that the system is notified about it..

Here are some details about the system:

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=4a0ef122-9e1d-4b72-bcd7-928b326d1a9e ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=1

$ uname -a
Linux devicename 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Finally one thing which works independently from both changes (i2c_i801 and modifying grub) is to switch to another tty like pressing CTRL+ALT+F3 and switching back with CTRL+ALT+F2. But I do not have any idea, what is loaded or unloaded after doing this.

Let me know if you need more details..

Revision history for this message
... (fabss) wrote :

sorry, in my last comment I didn't mean tty, I meant virtual terminal (vt)..

Revision history for this message
Mladen Ivkovic (mivkov) wrote :

I'm experiencing the same kind of issues on a Lenovo Thinkpad X1 and ubuntu 20.4.
Additionally, I can't do right clicks via two-finger touch after waking up again.

I was having an issue with the TTY earlier, and only now noticed that the issues rise up after the system went to sleep and woke up again. The TTY wouldn't load, all I get is a blinking cursor which doesn't respond to any keyboard input. I'm suspecting the issues are related, since both happen only after a wake up.

Revision history for this message
h3 (h3) wrote :

I'm using Ubuntu 20.04 on an old Lenovo Yoga and none of the workaround had any effect except adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in /etc/default/grub.

The only problem is that now it wont stay suspended.. It does go under suspend mode for like 3 seconds and wakes up immediatly, but at least the trackpad/nub still works.

sighs

Revision history for this message
h3 (h3) wrote :

If it can help anyone, this is a follow up on my issue. It seems the reason the laptop wouldn't stay suspended was caused by a USB device (even thought there were not any plugged in ..). You can find that using "dmesg | grep -i acpi" and then look into the wakup config using "cat /proc/acpi/wakeup".

Then you toggle devices until you find the problematic one using this command, in my case it was "XHC" so: `echo XHC > /proc/acpi/wakeup`. This will not overwrite the file, only toggle the relevant device.

When you found the culprit you can make that change permanent using "crontab -e" and adding this line: "@reboot echo XHC > /proc/acpi/wakeup". Otherwise the changes will be gone after next reboot.

Revision history for this message
Shobhit Singhal (shobhit55) wrote :

The issue for me was resolved in some recent system updates on Thinkpad X1 Carbon Gen 9. Just to let you know.

Revision history for this message
CaCO3 (caco3) wrote :

I still have this issue since years running Kubuntu on my Thinkpad T440s.
Current version: 22.04.1

Solution is always to run `sudo modprobe -r psmouse; sudo modprobe psmouse`

Revision history for this message
Gian Luca (gianluca-ricci) wrote :

Same issue with my Thinkpad X240 with Ubuntu 22.04.1

Workaround `sudo modprobe -r psmouse; sudo modprobe psmouse` still work

Revision history for this message
BeenD (doomd) wrote :

Same issue with my Thinkpad T14 AMD Gen 1 with Ubuntu 22.04.2

Workaround so far as above - sudo modprobe -r psmouse; sudo modprobe psmouse

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

Other bug subscribers

Remote bug watches

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