Bug 1508705 - Thinkpad W540 trackpad stops working after some time
Summary: Thinkpad W540 trackpad stops working after some time
Keywords:
Status: CLOSED DUPLICATE of bug 1442699
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-02 01:31 UTC by bztdlinux
Modified: 2018-03-13 19:01 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-13 19:01:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1485013 0 unspecified CLOSED Touchpad don't work after wake up from suspend 2024-11-10 17:30:14 UTC

Description bztdlinux 2017-11-02 01:31:56 UTC
Description of problem:
Trackpad and trackpoint stop responding until the rmi_smbus module is removed and reloaded. The following appears in dmesg:

[727301.468402] rmi4_physical rmi4-00: Failed to read irqs, code=-6
[728269.257401] rmi4_physical rmi4-00: Failed to read irqs, code=-6

Version-Release number of selected component (if applicable):
4.13 and later

How reproducible:
Always on 4.13, but can sometimes take days

Steps to Reproduce:
Use trackpad for some time (no obvious triggers, though it has yet to happen before the machine has been suspended at least once)

Additional info:
This may be related to bug 1485013, but it does not happen right on resume and the logs in dmesg are different.

Comment 1 Laura Abbott 2018-02-28 03:49:55 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 2 bztdlinux 2018-03-13 19:01:30 UTC

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


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