[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-04-13 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-12 Thread Christopher M. Penalver
Sergey Zolotarev: Given the nvidia drivers are a WORKAROUND, it appears the touchpad not working is correlated to an issue with the graphics driver nouveau. Hence, in order to upstream this, could you please remove the WORKAROUND, install the latest mainline kernel (now 4.16-rc1), reproduce, and

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-12 Thread Sergey Zolotarev
1) I've been using the drivers from NVIDIA with the normal (not mainline) kernel 4.13.0-32 for the past week and haven't had this touchpad issue. 2) When I resume from suspend the touchpad either works or it doesn't. It always stops working after I suspend/resume a few times. How much times can

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver
Sergey Zolotarev, to clarify, let us focus on the timeframe from since you installed Ubuntu a couple weeks ago to present. 1) To advise, it wouldn't hurt to see how things change when you use the nvidia proprietary driver. However, you will want to use the Ubuntu kernel (not mainline) before

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Sergey Zolotarev
I installed Ubuntu on this laptop a couple of weeks ago, so I can't say. But before Ubuntu I was using Fedora 27 for around 2 months and I didn't experience this problem there. I'm attaching dmesg output after another touchpad incident, from 4.15.1 this time. I hope it helps. It looks like this

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver
Sergey Zolotarev, to clarify, have you always had the issue of the display not working after waking up and you can't SSH into it, or is this something that started recently? ** Tags added: latest-bios-300 -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Sergey Zolotarev
I've installed the 4.15.1 kernel, what should I do next? I'm having the same pm_trace issue as before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746372 Title: [Asus K501UQ]

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver
Sergey Zolotarev, the latest mainline kernel is now 4.15.1. As per your logs, you were booted in the Ubuntu kernel. So that upstream may review, could you please provide the information with latest mainline? -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-03 Thread Sergey Zolotarev
** Attachment added: "dmesg when touchpad is not working after wakeup" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+attachment/5048491/+files/touchpad-dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-03 Thread Sergey Zolotarev
Could this be the cause? [ 4381.182926] irq 109: nobody cared (try booting with the "irqpoll" option) [ 4381.182932] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 4.13.0-32-generic #35-Ubuntu [ 4381.182933] Hardware name: ASUSTeK COMPUTER INC. K501UQ/K501UQ, BIOS K501UQ.300 09/13/2016

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-03 Thread Sergey Zolotarev
Unfortunately I can't perform steps 4-10 in the suspend debugging guide because the display is not working after waking up when doing pm_trace (it's turned off), and I can't SSH into the system from another computer because the network seems to be down as well (No route to host). When the laptop

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-03 Thread Sergey Zolotarev
1. The issue occurs when resuming from suspend. 2. Suspend by closing the lid. 3. Resume by lifting the lid. 4-10. Can't provide this information because I can't get to the console after waking up. 11. See suspend_stats.txt. 12. Can't SSH into the laptop after resume - ssh says "No route to

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-31 Thread Christopher M. Penalver
Sergey Zolotarev, please boot into latest mainline kernel with no patching/modifications, and provide the information from #5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746372

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-31 Thread Sergey Zolotarev
I was wrong, this didn't fix the bug. After a few more suspends and wakes the touchpad is dead again. I think it may depend on how many times the system is suspended or for how long it was suspended. ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-31 Thread Christopher M. Penalver
Sergey Zolotarev, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel (TO: Marcos Paulo de Souza, and Dmitry Torokhov CC: linux-input)? Please provide a direct URL to your post to

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-31 Thread Joseph Salisbury
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746372 Title: [Asus K501UQ] Touchpad stops working after suspend Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-31 Thread Sergey Zolotarev
This patch worked for me with v4.15 kernel: https://paste.ubuntu.com/26496011/ I basically found the old patch and added an entry for K501UQ there. The author changed his code from using DMI_PRODUCT_NAME to DMI_CHASSIS_TYPE since then but that doesn't work for my laptop apparently. -- You

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-30 Thread Christopher M. Penalver
Sergey Zolotarev, to advise, reports focus on one issue per report. This report is scoped to touchpad not working after suspend, not everything that may or may not work after suspend, or whatever other issues you may have. Despite this, could you please provide the missing information from

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-30 Thread Sergey Zolotarev
I installed the latest kernel (4.15) from http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.15/ but it didn't help. Touchpad worked for a few seconds after wakeup but then it stopped working. Also same issue with reboot again, don't know why you deleted it. ** Tags added:

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-01-30 Thread Christopher M. Penalver
Sergey Zolotarev, thank you for reporting this and helping make Ubuntu better. In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel available from