Bug 1552223 - Touchpad and Trackpoint does not work after resume
Summary: Touchpad and Trackpoint does not work after resume
Keywords:
Status: CLOSED DUPLICATE of bug 1548867
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-06 17:52 UTC by Hemant Kumar
Modified: 2018-03-06 20:44 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-06 20:44:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hemant Kumar 2018-03-06 17:52:09 UTC
After latest kernel update after resuming from sleep, both trackpoint and touchpad does not work on my Thinkpad T460p.

I am currently running:

Linux pern 4.15.6-200.fc26.x86_64 #1 SMP Mon Feb 26 18:51:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Output of lspci:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:16.3 Serial controller: Intel Corporation Sunrise Point-H KT Redirection (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)
03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)




Each time I try to move the touchpad/trackpoint I get:

Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:35 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16
Mar 06 12:48:36 pern kernel: rmi4_physical rmi4-00: Failed to read irqs, code=-16


printed in journalctl -f

Comment 1 Hemant Kumar 2018-03-06 17:53:14 UTC
This is clearly a regression, I am using same laptop with same Fedora 26 installation for awhile now.

Comment 2 Felix Kaechele 2018-03-06 20:44:00 UTC

*** This bug has been marked as a duplicate of bug 1548867 ***


Note You need to log in before you can comment on or make changes to this bug.