Touchpad not working after suspend/resume

Bug #1540430 reported by Uros Trojar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Touchpad not working after suspend/resume on Asus X302LA.

I have tried both workarounds in bug #1393079 to no success.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
Uname: Linux 3.19.0-47-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Mon Feb 1 16:26:19 2016
InstallationDate: Installed on 2016-01-31 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: uros 2656 F.... pulseaudio
 /dev/snd/controlC0: uros 2656 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=d2fb9926-f37b-400c-8fae-366846852756
InstallationDate: Installed on 2016-01-31 (52 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 003 Device 002: ID 8087:8001 Intel Corp.
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X302LA
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-56-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-56-generic N/A
 linux-backports-modules-3.19.0-56-generic N/A
 linux-firmware 1.127.20
Tags: trusty
Uname: Linux 3.19.0-56-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X302LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X302LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX302LA.204:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnX302LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X302LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Uros Trojar (uros-trojar) wrote :
Revision history for this message
Uros Trojar (uros-trojar) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1540430

affects: linux-lts-vivid (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Uros Trojar (uros-trojar) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Uros Trojar (uros-trojar) wrote : BootDmesg.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : CRDA.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : IwConfig.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : Lspci.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : ProcEnviron.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : ProcModules.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : PulseList.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : RfKill.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : UdevDb.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : UdevLog.txt

apport information

Revision history for this message
Uros Trojar (uros-trojar) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-204
Changed in linux (Ubuntu):
importance: Low → Medium
Revision history for this message
Uros Trojar (uros-trojar) wrote :

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.6.0-040600rc1

uname -a
Linux X302LA 4.6.0-040600rc1-generic #201603261930 SMP Sat Mar 26 23:32:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Uros Trojar (uros-trojar) wrote :

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.6.0-040600rc1

uname -a
Linux X302LA 4.6.0-040600rc1-generic #201603261930 SMP Sat Mar 26 23:32:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Uros Trojar (uros-trojar) wrote :

Which part of the process does the issue occur with, the suspend to ram, or resuming from?
Resuming from

Please advise how you suspended specifically. (all apply)
    Executing at a terminal pm-suspend
    Shutting the lid of your laptop, which is set to suspend on close.
    Clicking the word Suspend in the GUI.
    The computer suspends automatically on inactivity.

Please advise how you resumed specifically. Doesn't matter. Check already attached logs.

    Pressed the power button
    Lifted the lid
    Clicked a key on the keyboard

Revision history for this message
Uros Trojar (uros-trojar) wrote :

5.

uname -a
Linux X302LA 4.6.0-040600rc1-generic #201603261930 SMP Sat Mar 26 23:32:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

sudo su
echo freezer > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

6.

sudo su
echo devices > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

7.

sudo su
echo platform > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

8.

sudo su
echo processors > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

9.

sudo su
echo core > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

10.

sudo su
echo none > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

dmesg > dmesg.txt

Revision history for this message
Uros Trojar (uros-trojar) wrote :

11.

sudo cat /sys/kernel/debug/suspend_stats >suspend_stats

12.

N/A

Revision history for this message
Uros Trojar (uros-trojar) wrote :

latest Xorg.0.log

Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, to clarify, on which of the attached dmesg files is this problem reproducible with?

Also, the latest mainline kernel is now 4.6-rc2. You don't have to reattach everything, just test once to see if still reproducible or not, and then advise.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6-rc1
Revision history for this message
Uros Trojar (uros-trojar) wrote :

Hi Christopher,

I've upgraded to rc2 and the problem is still there. I've run sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" immediately after reboot into rc2 and the trackpad went dead.

Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, to clarify, on which of the attached dmesg files is this problem reproducible with?

Also, please continue to test the latest mainline kernel (now 4.6-rc4) to keep this report relevant to upstream.

Revision history for this message
Uros Trojar (uros-trojar) wrote :

Christopher, can you clarify. Do you need ALL of the dmesg files or just one? I can provide you with one relevant for rc4 if all of the specified confuses you.

Revision history for this message
penalvch (penalvch) wrote :

Uros Trojar, all of them (i.e. don't skip anything).

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.