Touchpad incorrectly recognized as PS/2 mouse in 'Lenovo ThinkPad 20DF004SMC'

Bug #1429446 reported by Martin Janiczek on 2015-03-07
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

Touchpad seen as a PS/2 mouse
- no gestures etc. work
- synclient says "Couldn't find synaptics properties. No synaptics driver loaded?"
- in "Mouse and Touchpad" settings the only device is "PS/2 Generic Mouse"
- in "Pointing devices" also.

System info:
- Manufacturer: LENOVO
- Product Name: 20DF004SMC
- Version: ThinkPad E550
- SKU Number: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550
- Family: ThinkPad E550

- System release: Xubuntu 14.10
- Linux version: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
- xserver-xorg-input-synaptics: 1.8.1-1ubuntu1

Various logs and diagnostics in attachment.
Please let me know if I can help with anything.
---
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: martin 2231 F.... pulseaudio
 /dev/snd/controlC1: martin 2231 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=8cc5836e-0d84-4d5c-9c7b-b25cecb6dd1e
InstallationDate: Installed on 2015-03-05 (2 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20DF004SMC
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=3fcadb61-bad7-4dfa-bf5f-ba6ef49cc31a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-31-generic N/A
 linux-backports-modules-3.16.0-31-generic N/A
 linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video
_MarkForUpload: True
dmi.bios.date: 01/22/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J5ET42WW (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20DF004SMC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJ5ET42WW(1.13):bd01/22/2015:svnLENOVO:pn20DF004SMC:pvrThinkPadE550:rvnLENOVO:rn20DF004SMC:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20DF004SMC
dmi.product.version: ThinkPad E550
dmi.sys.vendor: LENOVO

Martin Janiczek (janiczek) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1429446

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected utopic
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High

Martin Janiczek, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug 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-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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.

tags: added: latest-bios-1.13
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Martin Janiczek (janiczek) wrote :

Of course, will do later today!

Martin Janiczek (janiczek) wrote :

Tested these versions:
v4.0-rc3
v4.0-rc2
v4.0-rc1
v3.19.1

All the v4 versions kept crashing (didn't boot into X) on "Floating point exception" related (at least seeing "synaptics_drv" in the backtrace) to the touchpad - see the uploaded Xorg.failsafe.log from v4.0-rc1.

In v3.19.1:
- the touchpad works (gestures!)
- xinput says:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=11 [slave pointer (2)]
⎜ ↳ DualPoint Stick id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Integrated Camera id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]
- GPointing Device Settings shows both the stick and the touchpad
- Mouse and Touchpad also shows them both
- running `synclient` shows me config and not the error message

So far, from trying things out, it seems to work nice.
Will do the tagging you described.

Do you want me to upload some more logs, outputs etc?

tags: added: kernel-fixed-upstream kernel-fixed-upstream-3.19.1
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Martin Janiczek, the next step is to fully reverse commit bisect from kernel 3.16 to 3.19.1 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Martin Janiczek (janiczek) wrote :

v3.16.7 - BAD
v3.17-rc1 - GOOD

I'll be bisecting the commits later today; it's just a bit more time consuming than just trying out pre-build packages :)

Martin Janiczek (janiczek) wrote :

3808843cf10e4a696d942359d99822eff1a2de8e is the first bad commit
commit 3808843cf10e4a696d942359d99822eff1a2de8e
Author: Yunkang Tang <email address hidden>
Date: Sat Jul 26 13:51:41 2014 -0700

    Input: alps - add support for v7 devices

    Such as found on the new Toshiba Portégé Z30-A and Z40-A.

    Signed-off-by: Yunkang Tang <email address hidden>
    [<email address hidden>: Remove softbutton handling, this is done in userspace]
    [<email address hidden>: Report INPUT_PROP_BUTTONPAD]
    [<email address hidden>: Do not report fake PRESSURE, reporting BTN_TOUCH is
     enough]
    [<email address hidden>: Various cleanups / refactoring]
    Signed-off-by: Hans de Goede <email address hidden>
    Signed-off-by: Dmitry Torokhov <email address hidden>

:040000 040000 2531322660e7498daada6e9fbc18705c5f380de7 1733f378bbc3673deafdd46cb57b9ac1c59e1869 M drivers

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Martin Janiczek (janiczek) wrote :

(This is the output of git bisect - and because of using the git bisect for finding the fix, then if I understand correctly, this "first bad commit" is in reality the "first good commit"?)

The (not working) commit just before the fix is: c0cd17f6dc7342a81b61017e6b84e363f86081c6

tags: added: cherry-pick reverse-bisect-done
removed: needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers