Bug 101471 - Touchpad no longer detected on XPS 13 (9343)
Summary: Touchpad no longer detected on XPS 13 (9343)
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: I2C (show other bugs)
Hardware: IA-64 Linux
: P1 normal
Assignee: Drivers/I2C virtual user
URL:
Keywords:
: 101361 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-07-14 06:48 UTC by Christoph
Modified: 2016-01-20 23:45 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.2-rc2
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
dmesg for 4.2-rc2 (63.51 KB, application/octet-stream)
2015-07-14 06:48 UTC, Christoph 		Details
kernel bisect (1.21 KB, text/plain)
2015-07-31 21:00 UTC, davidryderuk@googlemail.com 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Christoph 2015-07-14 06:48:38 UTC 
Created attachment 182531 [details]
dmesg for 4.2-rc2

Booting my Dell XPS 13 (9343) with 4.2-rc2 the touchpad is no longer detected by the i2c_hid driver. Dmesg shows:

[    4.040117] i2c_designware INT3433:00: controller timed out
[    4.068461] i2c_designware INT3433:00: timeout in disabling adapter
[    4.068469] i2c_hid i2c-DLL0665:01: hid_descr_cmd failed

While booting with 4.1.1 it worked fine and dmesg showed:

[    3.051669] i2c_hid i2c-DLL0665:01: failed to retrieve report from device.
[    3.062036] i2c_hid i2c-DLL0665:01: failed to retrieve report from device.
[    3.062705] i2c_hid i2c-DLL0665:01: failed to retrieve report from device.
[    3.064201] i2c_hid i2c-DLL0665:01: failed to retrieve report from device.
[    3.064401] input: DLL0665:01 06CB:76AD UNKNOWN as /devices/pci0000:00/INT3433:00/i2c-9/i2c-DLL0665:01/0018:06CB:76AD.0002/input/input14
[    3.064527] hid-multitouch 0018:06CB:76AD.0002: input,hidraw1: <UNKNOWN> HID v1.00 Mouse [DLL0665:01 06CB:76AD] on
Comment 1 davidryderuk@googlemail.com 2015-07-24 16:28:28 UTC 
I have the same problem. 

There appears to be some differences in the /proc/interupts file.

This is with a working touchpad, in 4.1:
  7:       1367        168      17641        403  IR-IO-APIC-fasteoi  INT3432:00,INT3433:00
 39:         21          3        282          7  IR-IO-APIC  39-fasteoi  DLL0665:01

This is when the device is not working, in 4.2:
  7:         13          0          0          0  IR-IO-APIC   7-edge      INT3432:00, INT3433:00

I also noticed a similar bug (bug 82601) was fixed in the 3.17 development cycle.
Comment 2 davidryderuk@googlemail.com 2015-07-24 16:29:24 UTC 
*** Bug 101361 has been marked as a duplicate of this bug. ***
Comment 3 davidryderuk@googlemail.com 2015-07-31 20:58:50 UTC 
I have done a kernel bisect, and attached the relevant log file. 

I focused on a range of commits affecting IOAPIC related code, since this seemed to be at the center of a similar bug report in the 3.17 development cycle. 

The offending commit appears to be:
    commit d32932d02e1869be838cea3ace42467c360db377
    x86/irq: Convert IOAPIC to use hierarchical irqdomain interfaces

This was merged into the Linux mainline in the following merge:
    commit d70b3ef54ceaf1c7c92209f5a662a670d04cbed9
    Merge branch 'x86-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Comment 4 davidryderuk@googlemail.com 2015-07-31 21:00:57 UTC 
Created attachment 184081 [details]
kernel bisect
Comment 5 Mario Limonciello 2015-08-03 21:33:38 UTC 
It was mentioned today in #xps13 that this commit fixes the issue:
https://github.com/torvalds/linux/commit/646c4b75494747887f936513b669bb8a2d794459
Comment 6 davidryderuk@googlemail.com 2015-08-05 19:52:05 UTC 
Just a conformation that the problem has been fixed in Linux 4.2. 

Thanks for passing on the information.
Comment 7 Wolfram Sang 2016-01-20 23:44:53 UTC 
Reported fixed.
Note You need to log in before you can comment on or make changes to this bug.