Bug 1396845 - ELAN 1010 trackpad does not always work after suspend
Summary: ELAN 1010 trackpad does not always work after suspend
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-20 21:40 UTC by Jussi Eloranta
Modified: 2021-04-23 02:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 23:05:11 UTC
Type: Bug


Attachments (Terms of Use)

Description Jussi Eloranta 2016-11-20 21:40:49 UTC
Description of problem:

Sometimes ELAN 1010 trackpad does not come back properly after suspend. It acts like the left trackpad button is constantly pressed and dmesg shows the following:

[  825.308715] i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/28280)

After switching to another virtual screen and back restores the normal trackpad functionality.

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

This is with kernel 4.8.7-300.fc25.x86_64

Comment 1 Laura Abbott 2017-01-17 01:23:53 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 2 Laura Abbott 2017-02-23 23:05:11 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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