Bug 1250213

Summary:	Regression: Touchpad not recognized on boot since 4.1 kernel
Product:	[Fedora] Fedora	Reporter:	Piotr Popieluch <piotr1212>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	27	CC:	btissoir, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, muhammad.saad, piotr1212
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-23 16:45:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Piotr Popieluch 2015-08-04 18:15:20 UTC

Description of problem:
When booting up the system I cannot control the mouse cursor through the touchpad. This does not happen al the time but about 9 out of 10 boots. I can get the touchpad working again with:
# rmmod i2c_hid
# modprobe ic2_hid

On some boots the touchpad can only control the pointer horizontally, one time even I could only move the pointer to the right.

I have experienced this behavior before with older kernels, but then it happened once in about >20 boots, since 4.1 it happens 9 out of 10 boots. 

When freshly booted the touchpad does not show in xinput list, after reloading i2c_hid it does appear as it used to:
↳ DLL060A:00 06CB:2734        id=13	[slave  pointer  (2)]


Version-Release number of selected component (if applicable):
kernel-4.1.3-200.fc22.x86_64

Laptop is an Dell XPS 13 (9333)



How reproducible:
boot system

Steps to Reproduce:
1. boot system 
2. use touchpad
3.

Actual results:
cursor not moving


Expected results:
cursor moving


Additional info:
I've also noticed that the laptop does not go to sleep when closing the lid. Don't know if this is related but thought that maybe the lid button is on i2c too.

Comment 1 Justin M. Forbes 2015-10-20 19:19:25 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 2 Piotr Popieluch 2015-10-21 06:50:41 UTC

The touchpad gets recognized correctly on 4.2.3-200.fc22.x86_64 on boot.

Comment 3 Piotr Popieluch 2015-11-02 09:48:50 UTC

This occasionally still happens on boot. reopening bug.

Now running 4.2.3-200.fc22.x86_64

Comment 4 Piotr Popieluch 2015-11-02 17:48:02 UTC

Extra info, dmesg log:

[   23.499855] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[   23.499863] hid-rmi 0018:06CB:2734.0002: failed to write hid report (-121)
[   23.499866] hid-rmi 0018:06CB:2734.0002: rmi_set_page: set page failed: -121.
[   23.499869] hid-rmi 0018:06CB:2734.0002: failed to set page select to 0.
[   23.499957] input: DLL060A:00 06CB:2734 as /devices/pci0000:00/INT33C3:00/i2c-8/i2c-DLL060A:00/0018:06CB:2734.0002/input/input1085
[   23.500236] hid-rmi 0018:06CB:2734.0002: input,hidraw1: <UNKNOWN> HID v1.00 Pointer [DLL060A:00 06CB:2734] on 
[   23.500240] hid-rmi 0018:06CB:2734.0002: Device failed to be properly configured
[   23.503392] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[   23.503400] hid-rmi 0018:06CB:2734.0002: unable to set rmi mode to 1 (-121)

Comment 5 Piotr Popieluch 2015-11-14 10:47:32 UTC

Updated to f23, issue still exists.

Comment 6 Piotr Popieluch 2016-03-04 16:38:46 UTC

4.4 kernel still affected, dmesg log differs a bit:


[   24.877618] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[   24.877685] hid-rmi 0018:06CB:2734.0002: failed to write hid report (-121)
[   24.877746] hid-rmi 0018:06CB:2734.0002: failed to write request output report (-121)
[   24.879830] hid-rmi 0018:06CB:2734.0002: can not read f01 ctrl registers
[   24.881898] hid-rmi 0018:06CB:2734.0002: Error while initializing F01 (-121).
[   24.889771] hid-rmi 0018:06CB:2734.0002: hidraw1: I2C HID v1.00 Pointer [DLL060A:00 06CB:2734] on i2c-DLL060A:00
[   24.889777] hid-rmi 0018:06CB:2734.0002: Device failed to be properly configured

Comment 7 Laura Abbott 2016-09-23 19:22:36 UTC

*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 8 Piotr Popieluch 2016-09-25 20:40:26 UTC

still present on f24 and kernel 4.7

Comment 9 Justin M. Forbes 2017-04-11 14:40:43 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 10 Justin M. Forbes 2017-04-28 17:12:08 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 11 Piotr Popieluch 2017-11-20 09:39:11 UTC

Sorry for delay. Issue is still present on F25 with 4.13. dmesg now gives:


[    1.957123] usb 2-3: new full-speed USB device number 3 using xhci_hcd
[    2.075154] sdhci: Secure Digital Host Controller Interface driver
[    2.075155] sdhci: Copyright(c) Pierre Ossman
[    2.129255] usb 2-3: New USB device found, idVendor=06cb, idProduct=0af8
[    2.129258] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.129259] usb 2-3: Product: Synaptics Large Touch Screen
[    2.129261] usb 2-3: Manufacturer: SYNAPTICS
[    2.219387] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: s3203, fw id: 1522295
[    2.222589] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[    2.222640] hid-rmi 0018:06CB:2734.0004: failed to write hid report (-121)
[    2.222684] hid-rmi 0018:06CB:2734.0004: failed to write request output report (-121)
[    2.222736] rmi4_f01 rmi4-00.fn01: Failed to read F01 doze holdoff register: -121
[    2.222791] rmi4_f01: probe of rmi4-00.fn01 failed with error -121
[    2.227185] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[    2.227234] hid-rmi 0018:06CB:2734.0004: failed to write hid report (-121)
[    2.227280] hid-rmi 0018:06CB:2734.0004: failed to write request output report (-121)
[    2.227335] rmi4_f11: probe of rmi4-00.fn11 failed with error -121
[    2.251165] input: Synaptics (null) as /devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0004/input/input9
[    2.251384] hid-rmi 0018:06CB:2734.0004: input,hidraw3: I2C HID v1.00 Pointer [DLL060A:00 06CB:2734] on i2c-DLL060A:00
[    2.256046] psmouse serio1: synaptics: device claims to have extended capabilities, but I'm not able to read them.
[    2.261943] [drm] Memory usable by graphics device = 2048M
[    2.261946] checking generic (e0000000 7e9000) vs hw (e0000000 10000000)
[    2.261946] fb: switching to inteldrmfb from EFI VGA
[    2.261995] Console: switching to colour dummy device 80x25
[    2.262269] [drm] Replacing VGA console driver
[    2.268135] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.268136] [drm] Driver supports precise vblank timestamp query.
[    2.270529] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    2.280226] [drm] Initialized i915 1.6.0 20170619 for 0000:00:02.0 on minor 0
[    2.281438] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    2.281640] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
[    2.286094] usb 2-5: new high-speed USB device number 4 using xhci_hcd
[    2.297292] fbcon: inteldrmfb (fb0) is primary device
[    2.463137] psmouse serio1: synaptics: device claims to have extended capability 0x0c, but I'm not able to read it.
[    2.490739] usb 2-5: New USB device found, idVendor=0bda, idProduct=5752
[    2.490741] usb 2-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.490743] usb 2-5: Product: Integrated_Webcam_HD
[    2.490744] usb 2-5: Manufacturer: Generic
[    2.490745] usb 2-5: SerialNumber: 200901010001
[    2.651148] usb 2-6: new full-speed USB device number 5 using xhci_hcd
[    2.767293] clocksource: Switched to clocksource tsc
[    2.820462] usb 2-6: New USB device found, idVendor=8087, idProduct=07dc
[    2.820465] usb 2-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.832404] input: SYNAPTICS Synaptics Large Touch Screen as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/0003:06CB:0AF8.0005/input/input12
[    2.832497] hid-multitouch 0003:06CB:0AF8.0005: input,hiddev96,hidraw4: USB HID v1.11 Mouse [SYNAPTICS Synaptics Large Touch Screen] on usb-0000:00:14.0-3/input0
[    2.879137] psmouse serio1: synaptics: Unable to initialize device.
[    3.662860] Console: switching to colour frame buffer device 240x67
[    3.688798] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    6.778673] random: crng init done
[    8.463234] input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[    8.671156] psmouse serio1: Failed to enable mouse on isa0060/serio1

Comment 12 Piotr Popieluch 2017-11-20 10:14:55 UTC

Updated to F26, also showing rmi4_physical messages in dmesg.


[    1.956085] usb 2-3: Manufacturer: SYNAPTICS
[    2.057392] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[    2.057439] hid-rmi 0018:06CB:2734.0004: failed to write hid report (-121)
[    2.057481] hid-rmi 0018:06CB:2734.0004: rmi_set_page: set page failed: -121.
[    2.057525] rmi4_physical rmi4-00: Read PDT entry at 0x05e9 failed, code: -121.
[    2.057568] rmi4_physical rmi4-00: IRQ counting failed with code -121.
[    2.057612] rmi4_physical: probe of rmi4-00 failed with error -121

Comment 13 Piotr Popieluch 2017-11-25 13:53:57 UTC

With 4.13.13-300.fc27.x86_64:


[    1.981478] i2c_hid i2c-DLL060A:00: failed to set a report to device.
[    1.981524] hid-rmi 0018:06CB:2734.0002: failed to write hid report (-121)
[    1.981566] hid-rmi 0018:06CB:2734.0002: rmi_set_page: set page failed: -121.
[    1.981611] rmi4_physical rmi4-00: Read PDT entry at 0x02e9 failed, code: -121.
[    1.981656] rmi4_physical rmi4-00: IRQ counting failed with code -121.
[    1.981700] rmi4_physical: probe of rmi4-00 failed with error -121
[    1.981763] input: DLL060A:00 06CB:2734 as /devices/pci0000:00/INT33C3:00/i2c-0/i2c-DLL060A:00/0018:06CB:2734.0002/input/input12
[    1.982130] hid-rmi 0018:06CB:2734.0002: input,hidraw1: I2C HID v1.00 Pointer [DLL060A:00 06CB:2734] on i2c-DLL060A:00
[    2.023035] psmouse serio1: synaptics: Unable to query device: -1

Comment 14 Laura Abbott 2018-02-20 19:50:21 UTC

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 15 Laura Abbott 2018-03-23 16:45:42 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you did actually update, we apologize for the inconvenience (there are a lot of bugs). If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.