Re: T440s Synaptics clickpad: lost sync / KBC bad data

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[Vadim Fint]

Hello!

I was having exactly the same issues with brand new T440s from Lenovo. psmouse 
get lost sync every time I did a physical click on clickpad.

But for me that was HW issue: after disassembling notebook I saw touchpad 
cable was not snapped into touchpad at all. Because latch (with cable) moves 
2-3mm each click -- what was bad contact during that.

To deal with that issue I did removed only internal battery pack and locked a 
cable on touchpad with a screwdriver :) (15-20 minutes for whole operation)

Dont know what Windows internaly do with synaptics protocol, but there was no 
issues in Windows at all (but in recovery mode clickpad was not working at 
all).

Anyway, no problems in Gentoo with 3.12-3-pf kernel for me now! And no more 
that weird “out of sync” messages from psmouse at all.

Hope this helps!!

> Hello everyone,
> 
> I hope I'm at the right address here with my problems. If not, please do
> point me in the correct direction.
> 
> I have a Lenovo Thinkpad T440s with a Synaptics clickpad and an IBM
> trackpoint in it:
> 
> input: PS/2 Synaptics TouchPad as
> /devices/platform/i8042/serio1/input/input120 psmouse serio1: synaptics:
> Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x127c00,
> board id: 2668, fw id: 1293989 psmouse serio1: synaptics: serio: Synaptics
> pass-through port at isa0060/serio1/input0 input: SynPS/2 Synaptics
> TouchPad as /devices/platform/i8042/serio1/input/input123 psmouse serio34:
> alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64 psmouse serio34:
> trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 input: TPPS/2 IBM
> TrackPoint as /devices/platform/i8042/serio1/serio34/input/input124
> 
> The problem is that the trackpoint behaves incredibly erratic, sometimes
> working correctly for minutes at a time, sometimes just jumping around and
> many times just hanging. I need to remove and re-insert the psmouse module
> to solve that. Alongside this behaviour, my kernel log also is getting
> spammed with messages like:
> 
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 - driver resynced.
> and psmouse serio1: bad data from KBC - timeout
> 
> What I've tried:
> - Tried the kernel options i8042.nomux=1 and i8042.reset=1
> - Disable acpi by passing acpi=off to the kernel
> - Disabled CPU frequency scaling
> - Trying other protocols, e.g. by doing modprobe psmouse proto=imps or
> proto=bare - Switching from vanilla 3.12 kernel to both the latest&greatest
> kernel from Linus' Git and an antique 3.1.0 kernel - Turning on
> i8042.debug. To my untrained eye, it looks like bytes of PS/2 data are just
> disappearing when the 'lost sync' messages kick in. I can give an example
> of that if needed.
> 
> Strangely, the symptoms have been getting worse in the 10 days I've had this
> machine: from the first few days with no trouble to today with the mouse
> crapping out almost once every ten seconds or so. I would say it's a DOA
> and claim my warranty, if not frustratingly the machine works perfectly
> fine in Windows 8, with no touchpad trouble at all.
> 
> I'm willing to try things on this machine, run patches or take any hint in
> what I can change to get this working; if it helps I can even poke an
> oscilloscope at the PS2 lines. Not having a working touchpad or touchpoint
> is getting a bit frustrating...
> 
> Cheers,
> Jeroen

--
Regards,
Vadim Fint,
Moscow, Ru.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[Jan Bessai]

Hi all,

I'm having the same issue with a Lenovo T440p. The "lost sync" messages
occur if packets sent by the touchpad don't respect the bitmasks
specified in [1]. Adding some more debug output to the driver reveals,
that packages are garbled in a fairly random pattern, so just using the
less enforcing "SYN_NEWABS_RELAXED" bitmask
(drivers/input/mouse/synaptics.c:1165 , in accordance to manual section
6.1 last bullet point) does not help. Neither does cutting the packet
rate in halve or deactivating all wireless devices (=> not an
interference problem). As far as I can see, sleep flags are never set by
the driver, thus no luck with that either.
Interestingly my BIOS offers a switch to deactivate the touchpad and
just use the trackpoint. This however doesn't work either. As soon as I
trigger some (especially multi touch) activity, the touchpad comes back
and causes trouble. I believe the switch triggers pass-through mode
described in manual [1] section 5.3 and:

> A spontaneous reset of the TouchPad, due to internal sanity checks,
> ESD, or some other problem, will take the device out of transparent
> Pass-Through mode

Disabling the touchpad caused trouble for the Windows driver [2], too:
> <16.3.15.2>
> - (New) Fixed an issue where touchpad was still enabled after having
>   been disabled by BIOS.

I was able to reproduce the bug in the Windows 8 Professional installer,
the Debian 7.1 installer, the live CD version of the Ubuntu 14.04
(Trusty Tahr) daily build (14.01.2014, kernel 3.13.x) and my installed
Gentoo system (kernel 3.12.7). I'm not sure, but I think the touchpad
was acting a bit jumpy (but no where as bad) in the pre-installed
version of Windows 7 Professional as well.

For now I'm using the Bios switch to disable the touchpad in combination
with the psmouse module parameter "proto=exps". This allows me to just
use the trackpoint with a primitive ps2 mouse driver and leave the
touchpad disabled (at least if I'm careful enough not to accidentally
rest my palm on it). Being not careful enough however still causes it to
wake up and to inject timeout and bad parity errors, triggering the
cursor to jump around, click aimlessly and finally to hang. As soon as I
can afford to be without the laptop for a few days, I'll ask Lenovo to
replace the touchpad. I don't want to lose my warranty, otherwise I'd
open the notebook [3] and check if perhaps the cables are not in place
or broken. I'll also report back here, if there is anything new.

Greetings,
 Jan

[1]: Synaptics PS/2 TouchPad Interfacing Guide.
http://www.synaptics.com/sites/default/files/511-000275-01_RevB.pdf
[2]: Synaptics ThinkPad UltraNav Driver.
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/gggx45ww.txt
[3]: Video training for Lenovo T440p servicing.
http://lenovoservicetraining.com/content/CourseWarePublic/22088/player.html

T440s Synaptics clickpad: lost sync / KBC bad data

[J. Domburg]

Hello everyone,

I hope I'm at the right address here with my problems. If not, please do 
point me in the correct direction.

I have a Lenovo Thinkpad T440s with a Synaptics clickpad and an IBM 
trackpoint in it:

input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input120
psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2668, fw id: 1293989
psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input123
psmouse serio34: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
psmouse serio34: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3 input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio34/input/input124

The problem is that the trackpoint behaves incredibly erratic, sometimes 
working correctly for minutes at a time, sometimes just jumping around and 
many times just hanging. I need to remove and re-insert the psmouse module 
to solve that. Alongside this behaviour, my kernel log also is getting 
spammed with messages like:

psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
psmouse serio1: TouchPad at isa0060/serio1/input0 - driver resynced.
and 
psmouse serio1: bad data from KBC - timeout

What I've tried:
- Tried the kernel options i8042.nomux=1 and i8042.reset=1
- Disable acpi by passing acpi=off to the kernel
- Disabled CPU frequency scaling
- Trying other protocols, e.g. by doing modprobe psmouse proto=imps or 
proto=bare
- Switching from vanilla 3.12 kernel to both the latest&greatest kernel 
from Linus' Git and an antique 3.1.0 kernel
- Turning on i8042.debug. To my untrained eye, it looks like bytes of PS/2 
data are just disappearing when the 'lost sync' messages kick in. I can 
give an example of that if needed.

Strangely, the symptoms have been getting worse in the 10 days I've had 
this machine: from the first few days with no trouble to today with the 
mouse crapping out almost once every ten seconds or so. I would say it's a 
DOA and claim my warranty, if not frustratingly the machine works 
perfectly fine in Windows 8, with no touchpad trouble at all.

I'm willing to try things on this machine, run patches or take any hint in 
what I can change to get this working; if it helps I can even poke an 
oscilloscope at the PS2 lines. Not having a working touchpad or 
touchpoint is getting a bit frustrating...

Cheers,
Jeroen

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[Heinz Wiesinger]

J. Domburg <jeroen <at> spritesmods.com> writes:
> 
> Hello everyone,
> 
> I hope I'm at the right address here with my problems. If not, please do 
> point me in the correct direction.
> 
> I have a Lenovo Thinkpad T440s with a Synaptics clickpad and an IBM 
> trackpoint in it:
> 
> input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input120
> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 
0xd001a3/0x940300/0x127c00,
> board id: 2668, fw id: 1293989
> psmouse serio1: synaptics: serio: Synaptics pass-through port at 
isa0060/serio1/input0
> input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input123
> psmouse serio34: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
> psmouse serio34: trackpoint: IBM TrackPoint firmware: 0x0e, 
> buttons: 3/3 input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio34/input/input124
> 
> The problem is that the trackpoint behaves incredibly erratic, sometimes 
> working correctly for minutes at a time, sometimes just jumping around and 
> many times just hanging. I need to remove and re-insert the psmouse module 
> to solve that. Alongside this behaviour, my kernel log also is getting 
> spammed with messages like:
> 
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 - driver resynced.
> and 
> psmouse serio1: bad data from KBC - timeout
> 
> What I've tried:
> - Tried the kernel options i8042.nomux=1 and i8042.reset=1
> - Disable acpi by passing acpi=off to the kernel
> - Disabled CPU frequency scaling
> - Trying other protocols, e.g. by doing modprobe psmouse proto=imps or 
> proto=bare
> - Switching from vanilla 3.12 kernel to both the latest&greatest kernel 
> from Linus' Git and an antique 3.1.0 kernel
> - Turning on i8042.debug. To my untrained eye, it looks like bytes of PS/2 
> data are just disappearing when the 'lost sync' messages kick in. I can 
> give an example of that if needed.
> 
> Strangely, the symptoms have been getting worse in the 10 days I've had 
> this machine: from the first few days with no trouble to today with the 
> mouse crapping out almost once every ten seconds or so. I would say it's a 
> DOA and claim my warranty, if not frustratingly the machine works 
> perfectly fine in Windows 8, with no touchpad trouble at all.
> 
> I'm willing to try things on this machine, run patches or take any hint in 
> what I can change to get this working; if it helps I can even poke an 
> oscilloscope at the PS2 lines. Not having a working touchpad or 
> touchpoint is getting a bit frustrating...

I'm experiencing exactly the same issue. I have my T440s now for a bit more 
than two weeks. No issues with the touchpad until today when it suddenly 
started acting up and I now see messages like these in dmesg:

[ 2244.631822] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2668, fw id: 1293989
[ 2244.631830] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
[ 2244.668037] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input34
[ 2247.518110] psmouse serio8: alps: Unknown ALPS touchpad: E7=10 00 64, 
EC=10 00 64
[ 2248.807888] psmouse serio8: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[ 2249.016659] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio8/input/input35
[ 2254.649940] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2254.651179] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2254.652358] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2254.653594] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2254.663943] psmouse serio1: TouchPad at isa0060/serio1/input0 - driver 
resynced.
[ 2254.997536] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 4
[ 2254.998663] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2254.999790] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2255.000973] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2255.002107] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync 
at byte 1
[ 2255.002111] psmouse serio1: issuing reconnect request
[ 2255.131535] psmouse serio1: synaptics: Unable to query device.
[ 2255.598324] psmouse serio1: synaptics: device claims to have extended 
capability 0x0c, but I'm not able to read it.
[ 2255.643293] psmouse serio1: synaptics: Unable to initialize device.
[ 2255.767364] input: PS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input37
[ 2255.953314] psmouse serio1: synaptics: Unable to query device.

Same as Jeroen, I'm willing to try anything that might help resolve this 
situation.

Grs,
Heinz

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[J. Domburg]

On Sat, 21 Dec 2013, Heinz Wiesinger wrote:
> J. Domburg <jeroen <at> spritesmods.com> writes:
> I'm experiencing exactly the same issue. I have my T440s now for a bit more
> than two weeks. No issues with the touchpad until today when it suddenly
> started acting up and I now see messages like these in dmesg
<snip>

Hi Heinz, all,

Always good to know mine is not an isolated case, although in this case, I 
wouldn't want to wish the issue on anyone else...

FYI: I haven't resolved this issue yet, but I'm thinking this may be a 
hardware issue after all. I decided to try and see if Win7 has this issue 
too, and got myself an USB-stick to install it from. I didn't even get 
past the installer. It gave me exactly the same issues as Linux has: 
an erratic and finally hanging cursor when using the clickpad.

I can understand Lenovo not wanting to support a Linux-only-issue so up 
till now I haven't bothered them yet with my issue, but I can't see my 
laptop not having mouse support in something as commonly used and 
well-supported by hardware manufacturers as the Win7 installer. This 
smells like an hardware issue to me, so I filed a warranty case today.

If people here don't mind, I'll keep the list updated, if anything so 
other people running into the same issues will have a reference and know 
this isn't necessarily a kernel thing.

Depending on how Lenovo reacts, I'll either have a working laptop or a 
good reason to go soldering and probing the i2c bus. In any case, I should 
end up with a solution I'd think :) although it'd be good if someone more 
versed in the i8042 and related things would look over my shoulder in the 
latter case.

Cheers,
Jeroen

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[Heinz Wiesinger]

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

On Sunday 22 December 2013 00:17:06 you wrote:
> On Sat, 21 Dec 2013, Heinz Wiesinger wrote:
> > J. Domburg <jeroen <at> spritesmods.com> writes:
> > I'm experiencing exactly the same issue. I have my T440s now for a bit
> > more
> > than two weeks. No issues with the touchpad until today when it suddenly
> > started acting up and I now see messages like these in dmesg
> 
> <snip>
> 
> Hi Heinz, all,
> 
> Always good to know mine is not an isolated case, although in this case, I
> wouldn't want to wish the issue on anyone else...
> 
> FYI: I haven't resolved this issue yet, but I'm thinking this may be a
> hardware issue after all. I decided to try and see if Win7 has this issue
> too, and got myself an USB-stick to install it from. I didn't even get
> past the installer. It gave me exactly the same issues as Linux has:
> an erratic and finally hanging cursor when using the clickpad.
> 
> I can understand Lenovo not wanting to support a Linux-only-issue so up
> till now I haven't bothered them yet with my issue, but I can't see my
> laptop not having mouse support in something as commonly used and
> well-supported by hardware manufacturers as the Win7 installer. This
> smells like an hardware issue to me, so I filed a warranty case today.
> 
> If people here don't mind, I'll keep the list updated, if anything so
> other people running into the same issues will have a reference and know
> this isn't necessarily a kernel thing.
> 
> Depending on how Lenovo reacts, I'll either have a working laptop or a
> good reason to go soldering and probing the i2c bus. In any case, I should
> end up with a solution I'd think :) although it'd be good if someone more
> versed in the i8042 and related things would look over my shoulder in the
> latter case.

I ended up doing the same and just got their reply. They seem to be pretty 
adamant about it being a software issue, with the argument being if it were a 
hardware issue the clickpad would either be working fine or not working at all, 
but not on and off. Did you hear back from them as well?

Grs,
Heinz

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

Re: T440s Synaptics clickpad: lost sync / KBC bad data

[J. Domburg]

Hi all,

A last message about this issue, to help future people who find this 
data: In my case, it seems the problem was the hardware. For me the 
problem got increasingly worse, and also showed itself during a Win7 
installation and Win8 rescue session. Strangely, Windows 8 itself was less 
affected by the issue; maybe it has drivers that reset the Clickpad IC 
much quicker than Linux and the Windows installers.

With that data, I managed to convince Lenovo Support to exchange the 
clickpad hardware. (This means exchanging the complete keyboard bezel 
which means almost completely disassembling the machine, by the way...) 
The new clickpad has been working without _any_ lost sync byte for about a 
week now, so I'm a happy camper.

In the meantime, some other people have contacted me with the same issues. 
As far as I'm aware, they haven't solved it yet either by software or 
hardware exchange, but it may mean this is an issue a small amount of 
T440s's may have in general.

Anyway, sorry for the spam.

Cheers,
Jeroen

On Sun, 15 Dec 2013, J. Domburg wrote:

> Hello everyone,
>
> I hope I'm at the right address here with my problems. If not, please do 
> point me in the correct direction.
>
> I have a Lenovo Thinkpad T440s with a Synaptics clickpad and an IBM 
> trackpoint in it:
>
> input: PS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input120
> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 
> 0xd001a3/0x940300/0x127c00, board id: 2668, fw id: 1293989
> psmouse serio1: synaptics: serio: Synaptics pass-through port at 
> isa0060/serio1/input0
> input: SynPS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input123
> psmouse serio34: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
> psmouse serio34: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 
> input: TPPS/2 IBM TrackPoint as 
> /devices/platform/i8042/serio1/serio34/input/input124
>
> The problem is that the trackpoint behaves incredibly erratic, sometimes 
> working correctly for minutes at a time, sometimes just jumping around and 
> many times just hanging. I need to remove and re-insert the psmouse module to 
> solve that. Alongside this behaviour, my kernel log also is getting spammed 
> with messages like:
>
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
> psmouse serio1: TouchPad at isa0060/serio1/input0 - driver resynced.
> and psmouse serio1: bad data from KBC - timeout
>
> What I've tried:
> - Tried the kernel options i8042.nomux=1 and i8042.reset=1
> - Disable acpi by passing acpi=off to the kernel
> - Disabled CPU frequency scaling
> - Trying other protocols, e.g. by doing modprobe psmouse proto=imps or 
> proto=bare
> - Switching from vanilla 3.12 kernel to both the latest&greatest kernel from 
> Linus' Git and an antique 3.1.0 kernel
> - Turning on i8042.debug. To my untrained eye, it looks like bytes of PS/2 
> data are just disappearing when the 'lost sync' messages kick in. I can give 
> an example of that if needed.
>
> Strangely, the symptoms have been getting worse in the 10 days I've had this 
> machine: from the first few days with no trouble to today with the mouse 
> crapping out almost once every ten seconds or so. I would say it's a DOA and 
> claim my warranty, if not frustratingly the machine works perfectly fine in 
> Windows 8, with no touchpad trouble at all.
>
> I'm willing to try things on this machine, run patches or take any hint in 
> what I can change to get this working; if it helps I can even poke an 
> oscilloscope at the PS2 lines. Not having a working touchpad or touchpoint is 
> getting a bit frustrating...
>
> Cheers,
> Jeroen
>
>
>
>