You are not logged in.
Pages: 1
After some recent update (unfortunately, I can't quite point which one) touchpad started acting quite weird. I'll state everything I know.
My laptop is Dell Latitude 3470. I use libinput.
Sometimes after awake from suspend my touchpad stops working. Also, in recent few hours it's just stopped working just like that several times.
journalctl -xb shows this:
Aug 31 22:46:16 latitude kernel: i2c_designware i2c_designware.0: controller timed out
Aug 31 22:46:16 latitude kernel: i2c_designware i2c_designware.0: timeout in disabling adapter
Aug 31 22:46:16 latitude kernel: i2c_designware i2c_designware.0: timeout waiting for bus ready
...
(log is spamming last message several times per second)
...
Aug 31 22:46:19 latitude kernel: i2c_designware i2c_designware.0: controller timed out
...
(keeps printing this message every second)
Aug 31 22:48:03 latitude kernel: psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4704]
Aug 31 22:48:03 latitude kernel: psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1148..]
Aug 31 22:48:03 latitude kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN060c PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertou
Aug 31 22:48:03 latitude kernel: i2c_designware i2c_designware.0: controller timed out
Aug 31 22:48:03 latitude kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00a23/0x840300/0x12e800/0x0, board id: 3017, fw id: 1966826
Aug 31 22:48:03 latitude kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input98
Aug 31 22:48:03 latitude dbus[487]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.1" (uid=0 pid=486 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freed
Aug 31 22:48:04 latitude kernel: i2c_designware i2c_designware.0: controller timed out
(this is interesting, I don't have anything synaptic-related installed (I guess), and restarting psmouse doesn't help)
Aug 31 22:48:05 latitude kernel: i2c_designware i2c_designware.0: controller timed out
(keeps spamming this, but touchpad works now)
Aug 31 22:56:55 latitude kernel: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
Aug 31 22:56:55 latitude kernel: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
Aug 31 22:56:55 latitude kernel: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
Aug 31 22:56:55 latitude kernel: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
Aug 31 22:56:55 latitude kernel: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
Aug 31 22:56:55 latitude kernel: psmouse serio1: issuing reconnect request
Aug 31 22:56:56 latitude kernel: i2c_designware i2c_designware.0: controller timed out
Aug 31 22:56:56 latitude kernel: psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4704]
Aug 31 22:56:56 latitude kernel: psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1148..]
Aug 31 22:56:57 latitude kernel: i2c_designware i2c_designware.0: controller timed out
Now, this happened right now, but before this, only one of those 'i2c_designware ... controller timed out' was logged, and rmmod i2c_designware_platform followed by modprobe i2c-designware-platform helped. And synaptic is here for some weird reason.
I am really confused and don't know what to suspect. What additional info can I provide? Any suggestions about why this happens?
EDIT: Ok, I tried killing psmouse and it's seems that touchpad can't work without it. Restarting i2c_designware seem to calm it down, but synaptic is, eh... restarting after every long touchpad inactivity, which cause it to lag for a second. I am more confused with every second. This happened literally after last reboot.
EDIT2: After suspend, it's just stops and sometimes starts working randomly (only restarting i2c_designware modules seems to restore it), it's stopped printing anything in journalctl, but there is one piece of evidence in dmesg:
[ 6775.224372] i2c_hid i2c-DLL06F2:00: hid_descr_cmd failed
EDIT3: Could it be that system recognizes touchpad?
Sep 01 09:02:45 latitude kernel: input: DLL06F2:00 06CB:75DA Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-DLL06F2:00/0018:06CB:75DA.0003/input/input37
Sep 01 09:02:45 latitude kernel: hid-multitouch 0018:06CB:75DA.0003: input,hidraw0: I2C HID v1.00 Mouse [DLL06F2:00 06CB:75DA] on i2c-DLL06F2:00
EDIT4: After few reboots, I don't see any errors in dmesg or journalctl, but touchpad still stops working randomly, and SOMETIMES I still see this:
[Sep 1 10:30] i2c_designware i2c_designware.0: controller timed out
But currently, all that dmesg reports is:
[Sep 1 13:45] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ +0.000966] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ +0.001033] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ +0.025773] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ +0.001058] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ +0.000002] psmouse serio1: issuing reconnect request
[ +0.717055] psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4704]
[ +0.028327] psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1148..]
Last edited by SuperPrower (2017-09-01 10:49:50)
Offline
Ok, from what I read about last psmouse problem, it is mostly considered to be hardware issue, and this was confirmed by my touchpad going insane at one point, so I removed keyboard from my laptop, and double checked every cable, and, fair enough, touchpad clip or whatever was holding cable wasn't pressed, so I removed and inserted cable and pressed that clip, and it looks like that solved problem.
Offline
Pages: 1