Touchpad stopped working in 3.13.0-29

[Mathias Lagerwall]

After upgrading to 3.13.0-29 my touchpad and touchscreen stopped working. They worked fine in 3.13.0-27

Previous kernel:
Linux pixel 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[ 4.461093] atmel_mxt_ts 2-004a: Family ID: 162 Variant ID: 0 Major.Minor.Build: 2.0.AB
[ 4.461098] atmel_mxt_ts 2-004a: Matrix X Size: 32 Matrix Y Size: 52 Object Num: 33
[ 4.467564] input: Atmel maXTouch Touchscreen as /devices/pci0000:00/0000:00:02.0/i2c-2/2-004a/input/input9

[ 4.749053] atmel_mxt_ts 1-004b: Family ID: 130 Variant ID: 1 Major.Minor.Build: 1.0.AA
[ 4.749058] atmel_mxt_ts 1-004b: Matrix X Size: 18 Matrix Y Size: 12 Object Num: 22
[ 4.756586] input: Atmel maXTouch Touchpad as /devices/pci0000:00/0000:00:02.0/i2c-1/1-004b/input/input10

Current kernel:
Linux pixel 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
-- nothing with atmel --

Environment:
Description: Ubuntu 14.04 LTS
Release: 14.04
Chromebook Pixel

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mathias 1958 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 6 12:12:00 2014
HibernationDevice: RESUME=UUID=9bcd1b31-51d6-432f-b3f4-f22775882224
InstallationDate: Installed on 2014-06-04 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: GOOGLE Link
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=f0bc21ce-18f3-4d59-8265-1127a1863fb9 ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2012
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: dmi:bvncoreboot:bvr:bd12/10/2012:svnGOOGLE:pnLink:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Link
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Mathias Lagerwall, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (the one all the way at the top, and not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc8

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Mathias Lagerwall (mathias-lagerwall)]

Kernel
Linux pixel 3.15.0-031500rc8-generic #201406012235 SMP Mon Jun 2 02:36:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
fixed the problem.

[penalvch (penalvch)]

Mathias Lagewall, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise if this is reproducible?

[Mathias Lagerwall (mathias-lagerwall)]

The live cd image works fine, but it is an even older kernel in that one.
Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The problem seems to have occurred between 3.13.0-27 and 3.13.0-29

[penalvch (penalvch)]

Mathias Lagerwell:

>"The live cd image works fine, but it is an even older kernel in that one. Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"

 3.13.x is not the kernel available from the image noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327153/comments/5 .

>"The problem seems to have occurred between 3.13.0-27 and 3.13.0-29"

That was already clear from your Bug Description.

[Mathias Lagerwall (mathias-lagerwall)]

Sorry, this is the first time I am doing error reporting here, so please bare with me :)

I used your link above and downloaded:
utopic-desktop-amd64.iso 20-May-2014 07:53 1.0G Desktop image for 64-bit PC (AMD64) computers (standard download)

It gives:
ubuntu@ubuntu:~$ cat /etc/issue.net
Ubuntu Utopic Unicorn (development branch)
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Should I have taken the "utopic-desktop-amd64+mac.iso" instead?

Am I supposed to change the status every time I respond to "Confirmed" so it shows up on your radar, or is it enough that I respond?

[penalvch (penalvch)]

Mathias Lagerwall, did you actually install it, or just post from a live environment? If you didn't install it, that's why you would see the older kernel.

[Mathias Lagerwall (mathias-lagerwall)]

Oh, I didn't install it, just fired up the live cd. I thought they contained the same kernel version.
I don't really want to re-install the whole system since it is my main work computer. Can't I just install the kernel from somewhere?

[Mathias Lagerwall (mathias-lagerwall)]

Would it be helpful if I bisect the kernels in your link below to see which version it starts working again?
http://kernel.ubuntu.com/~kernel-ppa/mainline/

I am not sure how to determine the kernel version number from the names though. For example
v3.13.11.2-trusty is the last 3.13 version there. Is there a file inside the tells the ubuntu-version numbering?

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[penalvch (penalvch)]

Mathias Lagerwall, the next step is to fully commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Launchpad Janitor (janitor)]

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