Bug 1243609 - Elantech ETPS/2 touchpad doesn't work after suspend
Summary: Elantech ETPS/2 touchpad doesn't work after suspend
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-15 23:09 UTC by Jacek Sowiński
Modified: 2016-11-08 20:36 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:40:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (73.50 KB, text/plain)
2015-07-15 23:09 UTC, Jacek Sowiński
no flags Details
xinput list-props (works only before suspend) (1.83 KB, text/plain)
2015-07-15 23:11 UTC, Jacek Sowiński
no flags Details
xorg log (23.41 KB, text/plain)
2015-07-15 23:12 UTC, Jacek Sowiński
no flags Details
Disable i8042_controller_selftest() call on some Asus laptops (2.97 KB, patch)
2016-05-19 16:46 UTC, Jacek Sowiński
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 107971 0 None None None 2016-05-19 16:44:59 UTC

Description Jacek Sowiński 2015-07-15 23:09:36 UTC
Created attachment 1052491 [details]
dmesg output

I've bought yesterday ASUS R301LA Laptop equipped with Elantech ETPS/2 Touchpad (hardware version 4 with firmware version 0x381f00 according do dmesg). It'is recognized with both libinput or synaptics (latter with /usr/share/X11/xorg.conf.d/90-libinput.conf commented out or deleted) and works flawlessly without any hiccups. Unfortunately after resuming from suspend touchpad is dead:

- It's absent in `xinput list` output
- dmesg doesn't say anything about it on resume
- Xorg removes it after resume with message in Xorg.0.log:

> config/udev: removing device ETPS/2 Elantech Touchpad
> UnloadModlue: "synaptics"

- objects present before suspend in /sys/devices/platform/i8042/serio1/ (like reg_07 for instance) are absent after resume.

Steps to Reproduce:
1. power on, use touchpad with no problems
2. suspend (mem sleep)
3. resume

Actual results:
Touchpad is dead.


Expected results:
Touchpad should work without any problems, just like before suspend.

Comment 1 Jacek Sowiński 2015-07-15 23:11:31 UTC
Created attachment 1052492 [details]
xinput list-props (works only before suspend)

Comment 2 Jacek Sowiński 2015-07-15 23:12:40 UTC
Created attachment 1052493 [details]
xorg log

Comment 3 Justin M. Forbes 2015-10-20 19:07: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 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  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 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 4 Jacek Sowiński 2015-10-29 19:38:28 UTC
Bug is still present on 4.2.3-200.fc22. I'll provide info about F23 soon after its release.

Comment 5 atorlind 2016-03-04 20:09:49 UTC
Bug still present in Fedora 23 as of today. Affects Asus X302L as well. Symptoms as described - Works fine until suspend, after which it will not reawaken until reboot.

Comment 6 Jacek Sowiński 2016-05-19 16:37:08 UTC
Bug was also reported on upstream: https://bugzilla.kernel.org/show_bug.cgi?id=107971 and working patch for the issue has been posted there. I've slightly modified it to apply it on top of Fedora 23 v4.5 kernel and it works - touchpad now works after resuming from suspend.

Comment 7 Jacek Sowiński 2016-05-19 16:46:23 UTC
Created attachment 1159547 [details]
Disable i8042_controller_selftest() call on some Asus laptops

Comment 8 Laura Abbott 2016-09-23 19:19:43 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 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 9 Laura Abbott 2016-10-26 16:40:52 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.

Comment 10 Jacek Sowiński 2016-11-08 12:01:08 UTC
This bug is still present in kernel 4.8.4. However as far as I know it is fixed in kernel 4.9 and the fix is backported into kernel-4.8.6. As soon as I will update my machine to this version I'll review this bug.

Comment 11 Jacek Sowiński 2016-11-08 20:36:29 UTC
It is indeed fixed with kernel-core-4.8.6-201.fc24.x86_64.


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