After upgrading to 4.2.0.30 Elantech touchpad not detected

This change was made by a bot.

siulkilulki, thank you for reporting this and helping make Ubuntu better.

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.

I've installed and booted mainline 4.5.0-040500-generic #201603140130 as per the instructions. With this kernel, the touchpad is recognized and works.

Reported as bug #1559580

I started a kernel bisect between 4.2.0-27 and 4.2.0-30.

I built the first test kernel, up to the following commit:
ce0ef8e1f348a9ef7522429c1dd3295df131285e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Note, with this kernel, you have to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance

Thanks for your quick reply :-)

I've downloaded the kernel you built: I confirm that it is working up to commit ce0ef8e1f348a9ef7522429c1dd3295df131285e.

I built the first test kernel, up to the following commit:
d06fcd4940477fb1b0f52f23e7fe4d23d060c7fd

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

It also works with commit d06fcd4940477fb1b0f52f23e7fe4d23d060c7fd

I built the next test kernel, up to the following commit:
0f8e1864193330c04ce01ba9c9ee45e43e91f540

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Commit 0f8e1864193330c04ce01ba9c9ee45e43e91f540 does NOT work.

I built the next test kernel, up to the following commit:
cc0a33f849da5571bd1cae03bde0ac59f9fe9a45

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

I confirm that commit cc0a33f849da5571bd1cae03bde0ac59f9fe9a45 works.

I built the next test kernel, up to the following commit:
a7dbd2e3268627cedc6b10adc39b5e544a71655f

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

I confirm that commit a7dbd2e3268627cedc6b10adc39b5e544a71655f works.

I built the next test kernel, up to the following commit:
3e8e33a682b8c83b6079684834b1d6654c541df5

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

I confirm that commit 3e8e33a682b8c83b6079684834b1d6654c541df5 works.

I built the next test kernel, up to the following commit:
6f786b3b2e4c71f8d573d069411ec1a23c0b6bc3

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Commit 6f786b3b2e4c71f8d573d069411ec1a23c0b6bc3 does NOT work.

I built the next test kernel, up to the following commit:
0c07e5375a1bccb9c3acaedfadeb16fb8dd75760

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

I confirm that commit 0c07e5375a1bccb9c3acaedfadeb16fb8dd75760 works.

I built the next test kernel, up to the following commit:
78e5e67b89eec214d2a035865d31184ff8f6490b

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

I confirm that commit 78e5e67b89eec214d2a035865d31184ff8f6490b works.

The bisect reported that this is the first bad commit:

commit 6f786b3b2e4c71f8d573d069411ec1a23c0b6bc3
Author: Andy Shevchenko <email address hidden>
Date: Fri Dec 4 23:49:18 2015 +0200

    Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()"

I built a Wily test kernel with that commit reverted. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354

Can folks affected by this bug test this kernel and post back if it solves this bug?

Reverting the commit solves the problem. The 4.2.0-34 kernel without that commit works.

Is there anything else I can to help with this?

Me too. I didn't have time to check kernels, but now I'm eager to help.

2016-04-23 22:27 GMT+02:00 Thomas Zell <email address hidden>:

> Is there anything else I can to help with this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1549354
>
> Title:
> After upgrading to 4.2.0.30 Elantech touchpad not detected
>
> Status in linux package in Ubuntu:
> In Progress
> Status in linux source package in Wily:
> In Progress
>
> Bug description:
> Elan Touchpad not listed as "Elan Touchpad" after "xinput list" or "cat
> /proc/bus/input/devices"
> . Not detected properly? For sure it does not work.
> External mouse working well.
> Downgrading to 4.2.0-27-generic kernel solves problem(touchpad works).
> My computer model is Toshiba Chromebook 2 with Gnome ubuntu 15.10
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.10
> Package: linux-image-4.2.0-30-generic 4.2.0-30.35
> ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
> Uname: Linux 4.2.0-30-generic x86_64
> ApportVersion: 2.19.1-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: siulkilulki 909 F.... pulseaudio
> CurrentDesktop: GNOME
> Date: Wed Feb 24 16:55:47 2016
> InstallationDate: Installed on 2015-12-06 (80 days ago)
> InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 8087:07dc Intel Corp.
> Bus 001 Device 003: ID 04f2:b48b Chicony Electronics Co., Ltd
> Bus 001 Device 002: ID 1ea7:0011
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: GOOGLE Swanky
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic
> root=UUID=20463b36-edda-428c-a236-f715f1d7bb85 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.2.0-30-generic N/A
> linux-backports-modules-4.2.0-30-generic N/A
> linux-firmware 1.149.3
> SourcePackage: linux
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 08/22/2014
> dmi.bios.vendor: coreboot
> dmi.chassis.type: 3
> dmi.chassis.vendor: GOOGLE
> dmi.modalias:
> dmi:bvncoreboot:bvr:bd08/22/2014:svnGOOGLE:pnSwanky:pvr1.0:cvnGOOGLE:ct3:cvr:
> dmi.product.name: Swanky
> dmi.product.version: 1.0
> dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549354/+subscriptions
>

It appears this bug is a duplicate of bug 1562778. This fix for Wily should come in via that bug, so I'll mark this bug as a duplicate.

Well it may not be an exact duplicate because of different hardware. However, the same revert of a revert fixes both bug. There also appears to be a fix upstream that fixes this issue without the revert, so I'll build a test kernel and post a link to it shortly.

I built a Wily test kernel with a cherry pick of commit de16d55. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1549354/

Can you test this kernel and see if it resolves this bug?

I tested the new kernel 4.2.0-35 and it works.

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-wily' to 'verification-done-wily'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I confirm that the fix included in the wily-proposed kernel 4.2.0-37 works.

This bug was fixed in the package linux - 4.2.0-38.45

---------------
linux (4.2.0-38.45) wily; urgency=low

  [ Kamal Mostafa ]

  * CVE-2016-1583 (LP: #1588871)
    - ecryptfs: fix handling of directory opening
    - SAUCE: proc: prevent stacking filesystems on top
    - SAUCE: ecryptfs: forbid opening files without mmap handler
    - SAUCE: sched: panic on corrupted stack end

 -- Andy Whitcroft <email address hidden> Wed, 08 Jun 2016 22:10:39 +0100