* hid-multitouch stuck taps, possibly 4.5 regression?
@ 2016-03-15 21:47 Andy Lutomirski
2016-03-16 8:47 ` Benjamin Tissoires
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-03-15 21:47 UTC (permalink / raw)
To: Benjamin Tissoires, Mika Westerberg, linux-input, Jiri Kosina
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Hi-
In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
my XPS 13 9350's touchpad. The effect is that trying to left-click
ends up middle-clicking. I think it's a kernel issue and not a
hardware or libinput issue, but I'm not 100% sure. I don't think I
had this issue in 4.4.
I've attached what I think is an evtest issue of my fixing the issue
by pressing three fingers down in sequence and then releasing them.
After doing that, left-clicks worked.
--Andy
[-- Attachment #2: ev.txt --]
[-- Type: text/plain, Size: 8993 bytes --]
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x6cb product 0x76ae version 0x100
Input device name: "DLL0704:01 06CB:76AE Touchpad"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 325 (BTN_TOOL_FINGER)
Event code 328 (BTN_TOOL_QUINTTAP)
Event code 330 (BTN_TOUCH)
Event code 333 (BTN_TOOL_DOUBLETAP)
Event code 334 (BTN_TOOL_TRIPLETAP)
Event code 335 (BTN_TOOL_QUADTAP)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 1174
Min 0
Max 1216
Resolution 12
Event code 1 (ABS_Y)
Value 585
Min 0
Max 680
Resolution 12
Event code 47 (ABS_MT_SLOT)
Value 1
Min 0
Max 4
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 1216
Resolution 12
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 680
Resolution 12
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 0
Max 65535
Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 2 (INPUT_PROP_BUTTONPAD)
Testing ... (interrupt to exit)
Event: time 1458078092.092559, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1658
Event: time 1458078092.092559, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 359
Event: time 1458078092.092559, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 327
Event: time 1458078092.092559, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1458078092.092559, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1458078092.092559, -------------- SYN_REPORT ------------
Event: time 1458078092.232054, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
Event: time 1458078092.232054, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1659
Event: time 1458078092.232054, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 625
Event: time 1458078092.232054, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 270
Event: time 1458078092.232054, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1458078092.232054, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 1
Event: time 1458078092.232054, -------------- SYN_REPORT ------------
Event: time 1458078092.379317, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
Event: time 1458078092.379317, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 931
Event: time 1458078092.379317, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 287
Event: time 1458078092.379317, type 3 (EV_ABS), code 0 (ABS_X), value 931
Event: time 1458078092.379317, type 3 (EV_ABS), code 1 (ABS_Y), value 287
Event: time 1458078092.379317, -------------- SYN_REPORT ------------
Event: time 1458078092.758084, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1458078092.758084, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1458078092.758084, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 0
Event: time 1458078092.758084, type 3 (EV_ABS), code 0 (ABS_X), value 359
Event: time 1458078092.758084, type 3 (EV_ABS), code 1 (ABS_Y), value 327
Event: time 1458078092.758084, -------------- SYN_REPORT ------------
Event: time 1458078092.852128, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
Event: time 1458078092.852128, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1458078092.852128, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1458078092.852128, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1458078092.852128, -------------- SYN_REPORT ------------
Event: time 1458078093.018994, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1
Event: time 1458078093.018994, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1458078093.018994, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1458078093.018994, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1458078093.018994, -------------- SYN_REPORT ------------
Event: time 1458078093.297313, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
Event: time 1458078093.297313, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1660
Event: time 1458078093.297313, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 179
Event: time 1458078093.297313, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 654
Event: time 1458078093.297313, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1458078093.297313, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1458078093.297313, type 3 (EV_ABS), code 0 (ABS_X), value 179
Event: time 1458078093.297313, type 3 (EV_ABS), code 1 (ABS_Y), value 654
Event: time 1458078093.297313, -------------- SYN_REPORT ------------
Event: time 1458078093.348801, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 180
Event: time 1458078093.348801, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
Event: time 1458078093.348801, type 3 (EV_ABS), code 0 (ABS_X), value 180
Event: time 1458078093.348801, type 3 (EV_ABS), code 1 (ABS_Y), value 650
Event: time 1458078093.348801, -------------- SYN_REPORT ------------
Event: time 1458078093.355991, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
Event: time 1458078093.355991, type 3 (EV_ABS), code 1 (ABS_Y), value 649
Event: time 1458078093.355991, -------------- SYN_REPORT ------------
Event: time 1458078093.370723, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
Event: time 1458078093.370723, type 3 (EV_ABS), code 1 (ABS_Y), value 648
Event: time 1458078093.370723, -------------- SYN_REPORT ------------
Event: time 1458078093.377898, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
Event: time 1458078093.377898, type 3 (EV_ABS), code 1 (ABS_Y), value 647
Event: time 1458078093.377898, -------------- SYN_REPORT ------------
Event: time 1458078093.385184, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
Event: time 1458078093.385184, type 3 (EV_ABS), code 1 (ABS_Y), value 646
Event: time 1458078093.385184, -------------- SYN_REPORT ------------
Event: time 1458078093.399779, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645
Event: time 1458078093.399779, type 3 (EV_ABS), code 1 (ABS_Y), value 645
Event: time 1458078093.399779, -------------- SYN_REPORT ------------
Event: time 1458078093.407435, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1458078093.407435, -------------- SYN_REPORT ------------
Event: time 1458078093.450960, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
Event: time 1458078093.450960, type 3 (EV_ABS), code 1 (ABS_Y), value 646
Event: time 1458078093.450960, -------------- SYN_REPORT ------------
Event: time 1458078093.458260, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
Event: time 1458078093.458260, type 3 (EV_ABS), code 1 (ABS_Y), value 647
Event: time 1458078093.458260, -------------- SYN_REPORT ------------
Event: time 1458078093.465568, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
Event: time 1458078093.465568, type 3 (EV_ABS), code 1 (ABS_Y), value 648
Event: time 1458078093.465568, -------------- SYN_REPORT ------------
Event: time 1458078093.472880, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
Event: time 1458078093.472880, type 3 (EV_ABS), code 1 (ABS_Y), value 649
Event: time 1458078093.472880, -------------- SYN_REPORT ------------
Event: time 1458078093.480192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
Event: time 1458078093.480192, type 3 (EV_ABS), code 1 (ABS_Y), value 650
Event: time 1458078093.480192, -------------- SYN_REPORT ------------
Event: time 1458078093.487537, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 651
Event: time 1458078093.487537, type 3 (EV_ABS), code 1 (ABS_Y), value 651
Event: time 1458078093.487537, -------------- SYN_REPORT ------------
Event: time 1458078093.502119, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 652
Event: time 1458078093.502119, type 3 (EV_ABS), code 1 (ABS_Y), value 652
Event: time 1458078093.502119, -------------- SYN_REPORT ------------
Event: time 1458078093.538618, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1458078093.538618, -------------- SYN_REPORT ------------
Event: time 1458078093.618865, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 170
Event: time 1458078093.618865, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 680
Event: time 1458078093.618865, type 3 (EV_ABS), code 0 (ABS_X), value 170
Event: time 1458078093.618865, type 3 (EV_ABS), code 1 (ABS_Y), value 680
Event: time 1458078093.618865, -------------- SYN_REPORT ------------
Event: time 1458078093.662013, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1458078093.662013, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1458078093.662013, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1458078093.662013, -------------- SYN_REPORT ------------
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-15 21:47 hid-multitouch stuck taps, possibly 4.5 regression? Andy Lutomirski
@ 2016-03-16 8:47 ` Benjamin Tissoires
2016-03-16 21:59 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Benjamin Tissoires @ 2016-03-16 8:47 UTC (permalink / raw)
To: Andy Lutomirski; +Cc: Mika Westerberg, linux-input, Jiri Kosina
Hi Andy,
On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
> Hi-
>
> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
> my XPS 13 9350's touchpad. The effect is that trying to left-click
> ends up middle-clicking. I think it's a kernel issue and not a
> hardware or libinput issue, but I'm not 100% sure. I don't think I
> had this issue in 4.4.
>
> I've attached what I think is an evtest issue of my fixing the issue
> by pressing three fingers down in sequence and then releasing them.
> After doing that, left-clicks worked.
I think I already have been reported the issue here:
https://bugs.freedesktop.org/show_bug.cgi?id=93948
The result was that it was more likely an I2C transport bug than a
hid-multitouch one (see comment #8 in the fdo bug).
You can try to run hid-recorder when you see the problems, and then
parse the output (or just send it to me). There is huge chances that
there will be no events from I2C sending the release.
And again, I am not sure how we could end up debugging this in the
i2c-designware driver :(
Cheers,
Benjamin
>
> --Andy
> Input driver version is 1.0.1
> Input device ID: bus 0x18 vendor 0x6cb product 0x76ae version 0x100
> Input device name: "DLL0704:01 06CB:76AE Touchpad"
> Supported events:
> Event type 0 (EV_SYN)
> Event type 1 (EV_KEY)
> Event code 272 (BTN_LEFT)
> Event code 325 (BTN_TOOL_FINGER)
> Event code 328 (BTN_TOOL_QUINTTAP)
> Event code 330 (BTN_TOUCH)
> Event code 333 (BTN_TOOL_DOUBLETAP)
> Event code 334 (BTN_TOOL_TRIPLETAP)
> Event code 335 (BTN_TOOL_QUADTAP)
> Event type 3 (EV_ABS)
> Event code 0 (ABS_X)
> Value 1174
> Min 0
> Max 1216
> Resolution 12
> Event code 1 (ABS_Y)
> Value 585
> Min 0
> Max 680
> Resolution 12
> Event code 47 (ABS_MT_SLOT)
> Value 1
> Min 0
> Max 4
> Event code 53 (ABS_MT_POSITION_X)
> Value 0
> Min 0
> Max 1216
> Resolution 12
> Event code 54 (ABS_MT_POSITION_Y)
> Value 0
> Min 0
> Max 680
> Resolution 12
> Event code 57 (ABS_MT_TRACKING_ID)
> Value 0
> Min 0
> Max 65535
> Properties:
> Property type 0 (INPUT_PROP_POINTER)
> Property type 2 (INPUT_PROP_BUTTONPAD)
> Testing ... (interrupt to exit)
> Event: time 1458078092.092559, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1658
> Event: time 1458078092.092559, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 359
> Event: time 1458078092.092559, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 327
> Event: time 1458078092.092559, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
> Event: time 1458078092.092559, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
> Event: time 1458078092.092559, -------------- SYN_REPORT ------------
> Event: time 1458078092.232054, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
> Event: time 1458078092.232054, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1659
> Event: time 1458078092.232054, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 625
> Event: time 1458078092.232054, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 270
> Event: time 1458078092.232054, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
> Event: time 1458078092.232054, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 1
> Event: time 1458078092.232054, -------------- SYN_REPORT ------------
> Event: time 1458078092.379317, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
> Event: time 1458078092.379317, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 931
> Event: time 1458078092.379317, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 287
> Event: time 1458078092.379317, type 3 (EV_ABS), code 0 (ABS_X), value 931
> Event: time 1458078092.379317, type 3 (EV_ABS), code 1 (ABS_Y), value 287
> Event: time 1458078092.379317, -------------- SYN_REPORT ------------
> Event: time 1458078092.758084, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
> Event: time 1458078092.758084, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
> Event: time 1458078092.758084, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 0
> Event: time 1458078092.758084, type 3 (EV_ABS), code 0 (ABS_X), value 359
> Event: time 1458078092.758084, type 3 (EV_ABS), code 1 (ABS_Y), value 327
> Event: time 1458078092.758084, -------------- SYN_REPORT ------------
> Event: time 1458078092.852128, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
> Event: time 1458078092.852128, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
> Event: time 1458078092.852128, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
> Event: time 1458078092.852128, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
> Event: time 1458078092.852128, -------------- SYN_REPORT ------------
> Event: time 1458078093.018994, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1
> Event: time 1458078093.018994, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
> Event: time 1458078093.018994, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
> Event: time 1458078093.018994, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
> Event: time 1458078093.018994, -------------- SYN_REPORT ------------
> Event: time 1458078093.297313, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
> Event: time 1458078093.297313, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1660
> Event: time 1458078093.297313, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 179
> Event: time 1458078093.297313, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 654
> Event: time 1458078093.297313, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
> Event: time 1458078093.297313, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
> Event: time 1458078093.297313, type 3 (EV_ABS), code 0 (ABS_X), value 179
> Event: time 1458078093.297313, type 3 (EV_ABS), code 1 (ABS_Y), value 654
> Event: time 1458078093.297313, -------------- SYN_REPORT ------------
> Event: time 1458078093.348801, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 180
> Event: time 1458078093.348801, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
> Event: time 1458078093.348801, type 3 (EV_ABS), code 0 (ABS_X), value 180
> Event: time 1458078093.348801, type 3 (EV_ABS), code 1 (ABS_Y), value 650
> Event: time 1458078093.348801, -------------- SYN_REPORT ------------
> Event: time 1458078093.355991, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
> Event: time 1458078093.355991, type 3 (EV_ABS), code 1 (ABS_Y), value 649
> Event: time 1458078093.355991, -------------- SYN_REPORT ------------
> Event: time 1458078093.370723, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
> Event: time 1458078093.370723, type 3 (EV_ABS), code 1 (ABS_Y), value 648
> Event: time 1458078093.370723, -------------- SYN_REPORT ------------
> Event: time 1458078093.377898, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
> Event: time 1458078093.377898, type 3 (EV_ABS), code 1 (ABS_Y), value 647
> Event: time 1458078093.377898, -------------- SYN_REPORT ------------
> Event: time 1458078093.385184, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
> Event: time 1458078093.385184, type 3 (EV_ABS), code 1 (ABS_Y), value 646
> Event: time 1458078093.385184, -------------- SYN_REPORT ------------
> Event: time 1458078093.399779, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645
> Event: time 1458078093.399779, type 3 (EV_ABS), code 1 (ABS_Y), value 645
> Event: time 1458078093.399779, -------------- SYN_REPORT ------------
> Event: time 1458078093.407435, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
> Event: time 1458078093.407435, -------------- SYN_REPORT ------------
> Event: time 1458078093.450960, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
> Event: time 1458078093.450960, type 3 (EV_ABS), code 1 (ABS_Y), value 646
> Event: time 1458078093.450960, -------------- SYN_REPORT ------------
> Event: time 1458078093.458260, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
> Event: time 1458078093.458260, type 3 (EV_ABS), code 1 (ABS_Y), value 647
> Event: time 1458078093.458260, -------------- SYN_REPORT ------------
> Event: time 1458078093.465568, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
> Event: time 1458078093.465568, type 3 (EV_ABS), code 1 (ABS_Y), value 648
> Event: time 1458078093.465568, -------------- SYN_REPORT ------------
> Event: time 1458078093.472880, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
> Event: time 1458078093.472880, type 3 (EV_ABS), code 1 (ABS_Y), value 649
> Event: time 1458078093.472880, -------------- SYN_REPORT ------------
> Event: time 1458078093.480192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
> Event: time 1458078093.480192, type 3 (EV_ABS), code 1 (ABS_Y), value 650
> Event: time 1458078093.480192, -------------- SYN_REPORT ------------
> Event: time 1458078093.487537, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 651
> Event: time 1458078093.487537, type 3 (EV_ABS), code 1 (ABS_Y), value 651
> Event: time 1458078093.487537, -------------- SYN_REPORT ------------
> Event: time 1458078093.502119, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 652
> Event: time 1458078093.502119, type 3 (EV_ABS), code 1 (ABS_Y), value 652
> Event: time 1458078093.502119, -------------- SYN_REPORT ------------
> Event: time 1458078093.538618, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
> Event: time 1458078093.538618, -------------- SYN_REPORT ------------
> Event: time 1458078093.618865, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 170
> Event: time 1458078093.618865, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 680
> Event: time 1458078093.618865, type 3 (EV_ABS), code 0 (ABS_X), value 170
> Event: time 1458078093.618865, type 3 (EV_ABS), code 1 (ABS_Y), value 680
> Event: time 1458078093.618865, -------------- SYN_REPORT ------------
> Event: time 1458078093.662013, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
> Event: time 1458078093.662013, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
> Event: time 1458078093.662013, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
> Event: time 1458078093.662013, -------------- SYN_REPORT ------------
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-16 8:47 ` Benjamin Tissoires
@ 2016-03-16 21:59 ` Andy Lutomirski
2016-03-17 8:06 ` Mika Westerberg
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-03-16 21:59 UTC (permalink / raw)
To: Benjamin Tissoires
Cc: Mika Westerberg, linux-input, Jiri Kosina, Jingoo Han, Pratyush Anand
[add i2c-designware maintainers]
On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
> Hi Andy,
>
> On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>> Hi-
>>
>> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>> my XPS 13 9350's touchpad. The effect is that trying to left-click
>> ends up middle-clicking. I think it's a kernel issue and not a
>> hardware or libinput issue, but I'm not 100% sure. I don't think I
>> had this issue in 4.4.
>>
>> I've attached what I think is an evtest issue of my fixing the issue
>> by pressing three fingers down in sequence and then releasing them.
>> After doing that, left-clicks worked.
>
> I think I already have been reported the issue here:
> https://bugs.freedesktop.org/show_bug.cgi?id=93948
>
> The result was that it was more likely an I2C transport bug than a
> hid-multitouch one (see comment #8 in the fdo bug).
>
> You can try to run hid-recorder when you see the problems, and then
> parse the output (or just send it to me). There is huge chances that
> there will be no events from I2C sending the release.
>
> And again, I am not sure how we could end up debugging this in the
> i2c-designware driver :(
>
Does this ring a bell?
--Andy
> Cheers,
> Benjamin
>
>>
>> --Andy
>
>> Input driver version is 1.0.1
>> Input device ID: bus 0x18 vendor 0x6cb product 0x76ae version 0x100
>> Input device name: "DLL0704:01 06CB:76AE Touchpad"
>> Supported events:
>> Event type 0 (EV_SYN)
>> Event type 1 (EV_KEY)
>> Event code 272 (BTN_LEFT)
>> Event code 325 (BTN_TOOL_FINGER)
>> Event code 328 (BTN_TOOL_QUINTTAP)
>> Event code 330 (BTN_TOUCH)
>> Event code 333 (BTN_TOOL_DOUBLETAP)
>> Event code 334 (BTN_TOOL_TRIPLETAP)
>> Event code 335 (BTN_TOOL_QUADTAP)
>> Event type 3 (EV_ABS)
>> Event code 0 (ABS_X)
>> Value 1174
>> Min 0
>> Max 1216
>> Resolution 12
>> Event code 1 (ABS_Y)
>> Value 585
>> Min 0
>> Max 680
>> Resolution 12
>> Event code 47 (ABS_MT_SLOT)
>> Value 1
>> Min 0
>> Max 4
>> Event code 53 (ABS_MT_POSITION_X)
>> Value 0
>> Min 0
>> Max 1216
>> Resolution 12
>> Event code 54 (ABS_MT_POSITION_Y)
>> Value 0
>> Min 0
>> Max 680
>> Resolution 12
>> Event code 57 (ABS_MT_TRACKING_ID)
>> Value 0
>> Min 0
>> Max 65535
>> Properties:
>> Property type 0 (INPUT_PROP_POINTER)
>> Property type 2 (INPUT_PROP_BUTTONPAD)
>> Testing ... (interrupt to exit)
>> Event: time 1458078092.092559, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1658
>> Event: time 1458078092.092559, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 359
>> Event: time 1458078092.092559, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 327
>> Event: time 1458078092.092559, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
>> Event: time 1458078092.092559, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
>> Event: time 1458078092.092559, -------------- SYN_REPORT ------------
>> Event: time 1458078092.232054, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
>> Event: time 1458078092.232054, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1659
>> Event: time 1458078092.232054, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 625
>> Event: time 1458078092.232054, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 270
>> Event: time 1458078092.232054, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
>> Event: time 1458078092.232054, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 1
>> Event: time 1458078092.232054, -------------- SYN_REPORT ------------
>> Event: time 1458078092.379317, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
>> Event: time 1458078092.379317, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 931
>> Event: time 1458078092.379317, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 287
>> Event: time 1458078092.379317, type 3 (EV_ABS), code 0 (ABS_X), value 931
>> Event: time 1458078092.379317, type 3 (EV_ABS), code 1 (ABS_Y), value 287
>> Event: time 1458078092.379317, -------------- SYN_REPORT ------------
>> Event: time 1458078092.758084, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
>> Event: time 1458078092.758084, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
>> Event: time 1458078092.758084, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 0
>> Event: time 1458078092.758084, type 3 (EV_ABS), code 0 (ABS_X), value 359
>> Event: time 1458078092.758084, type 3 (EV_ABS), code 1 (ABS_Y), value 327
>> Event: time 1458078092.758084, -------------- SYN_REPORT ------------
>> Event: time 1458078092.852128, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 2
>> Event: time 1458078092.852128, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
>> Event: time 1458078092.852128, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
>> Event: time 1458078092.852128, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
>> Event: time 1458078092.852128, -------------- SYN_REPORT ------------
>> Event: time 1458078093.018994, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1
>> Event: time 1458078093.018994, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
>> Event: time 1458078093.018994, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
>> Event: time 1458078093.018994, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
>> Event: time 1458078093.018994, -------------- SYN_REPORT ------------
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 0
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1660
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 179
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 654
>> Event: time 1458078093.297313, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
>> Event: time 1458078093.297313, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 0 (ABS_X), value 179
>> Event: time 1458078093.297313, type 3 (EV_ABS), code 1 (ABS_Y), value 654
>> Event: time 1458078093.297313, -------------- SYN_REPORT ------------
>> Event: time 1458078093.348801, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 180
>> Event: time 1458078093.348801, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
>> Event: time 1458078093.348801, type 3 (EV_ABS), code 0 (ABS_X), value 180
>> Event: time 1458078093.348801, type 3 (EV_ABS), code 1 (ABS_Y), value 650
>> Event: time 1458078093.348801, -------------- SYN_REPORT ------------
>> Event: time 1458078093.355991, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
>> Event: time 1458078093.355991, type 3 (EV_ABS), code 1 (ABS_Y), value 649
>> Event: time 1458078093.355991, -------------- SYN_REPORT ------------
>> Event: time 1458078093.370723, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
>> Event: time 1458078093.370723, type 3 (EV_ABS), code 1 (ABS_Y), value 648
>> Event: time 1458078093.370723, -------------- SYN_REPORT ------------
>> Event: time 1458078093.377898, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
>> Event: time 1458078093.377898, type 3 (EV_ABS), code 1 (ABS_Y), value 647
>> Event: time 1458078093.377898, -------------- SYN_REPORT ------------
>> Event: time 1458078093.385184, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
>> Event: time 1458078093.385184, type 3 (EV_ABS), code 1 (ABS_Y), value 646
>> Event: time 1458078093.385184, -------------- SYN_REPORT ------------
>> Event: time 1458078093.399779, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 645
>> Event: time 1458078093.399779, type 3 (EV_ABS), code 1 (ABS_Y), value 645
>> Event: time 1458078093.399779, -------------- SYN_REPORT ------------
>> Event: time 1458078093.407435, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
>> Event: time 1458078093.407435, -------------- SYN_REPORT ------------
>> Event: time 1458078093.450960, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 646
>> Event: time 1458078093.450960, type 3 (EV_ABS), code 1 (ABS_Y), value 646
>> Event: time 1458078093.450960, -------------- SYN_REPORT ------------
>> Event: time 1458078093.458260, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 647
>> Event: time 1458078093.458260, type 3 (EV_ABS), code 1 (ABS_Y), value 647
>> Event: time 1458078093.458260, -------------- SYN_REPORT ------------
>> Event: time 1458078093.465568, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 648
>> Event: time 1458078093.465568, type 3 (EV_ABS), code 1 (ABS_Y), value 648
>> Event: time 1458078093.465568, -------------- SYN_REPORT ------------
>> Event: time 1458078093.472880, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 649
>> Event: time 1458078093.472880, type 3 (EV_ABS), code 1 (ABS_Y), value 649
>> Event: time 1458078093.472880, -------------- SYN_REPORT ------------
>> Event: time 1458078093.480192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 650
>> Event: time 1458078093.480192, type 3 (EV_ABS), code 1 (ABS_Y), value 650
>> Event: time 1458078093.480192, -------------- SYN_REPORT ------------
>> Event: time 1458078093.487537, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 651
>> Event: time 1458078093.487537, type 3 (EV_ABS), code 1 (ABS_Y), value 651
>> Event: time 1458078093.487537, -------------- SYN_REPORT ------------
>> Event: time 1458078093.502119, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 652
>> Event: time 1458078093.502119, type 3 (EV_ABS), code 1 (ABS_Y), value 652
>> Event: time 1458078093.502119, -------------- SYN_REPORT ------------
>> Event: time 1458078093.538618, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
>> Event: time 1458078093.538618, -------------- SYN_REPORT ------------
>> Event: time 1458078093.618865, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 170
>> Event: time 1458078093.618865, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 680
>> Event: time 1458078093.618865, type 3 (EV_ABS), code 0 (ABS_X), value 170
>> Event: time 1458078093.618865, type 3 (EV_ABS), code 1 (ABS_Y), value 680
>> Event: time 1458078093.618865, -------------- SYN_REPORT ------------
>> Event: time 1458078093.662013, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
>> Event: time 1458078093.662013, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
>> Event: time 1458078093.662013, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
>> Event: time 1458078093.662013, -------------- SYN_REPORT ------------
>
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-16 21:59 ` Andy Lutomirski
@ 2016-03-17 8:06 ` Mika Westerberg
2016-03-17 18:43 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Mika Westerberg @ 2016-03-17 8:06 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Benjamin Tissoires, linux-input, Jiri Kosina, Jingoo Han, Pratyush Anand
On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
> [add i2c-designware maintainers]
>
> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
> > Hi Andy,
> >
> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
> >> Hi-
> >>
> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
> >> ends up middle-clicking. I think it's a kernel issue and not a
> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
> >> had this issue in 4.4.
> >>
> >> I've attached what I think is an evtest issue of my fixing the issue
> >> by pressing three fingers down in sequence and then releasing them.
> >> After doing that, left-clicks worked.
> >
> > I think I already have been reported the issue here:
> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
> >
> > The result was that it was more likely an I2C transport bug than a
> > hid-multitouch one (see comment #8 in the fdo bug).
> >
> > You can try to run hid-recorder when you see the problems, and then
> > parse the output (or just send it to me). There is huge chances that
> > there will be no events from I2C sending the release.
> >
> > And again, I am not sure how we could end up debugging this in the
> > i2c-designware driver :(
> >
>
> Does this ring a bell?
i2c-designware usually prints errors to dmesg if it fails to transfer
messages. Can you include dmesg of the failure as well?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-17 8:06 ` Mika Westerberg
@ 2016-03-17 18:43 ` Andy Lutomirski
2016-03-17 20:24 ` Andrew Duggan
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-03-17 18:43 UTC (permalink / raw)
To: Mika Westerberg
Cc: Benjamin Tissoires, linux-input, Jiri Kosina, Jingoo Han, Pratyush Anand
On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>> [add i2c-designware maintainers]
>>
>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>> > Hi Andy,
>> >
>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>> >> Hi-
>> >>
>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>> >> ends up middle-clicking. I think it's a kernel issue and not a
>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>> >> had this issue in 4.4.
>> >>
>> >> I've attached what I think is an evtest issue of my fixing the issue
>> >> by pressing three fingers down in sequence and then releasing them.
>> >> After doing that, left-clicks worked.
>> >
>> > I think I already have been reported the issue here:
>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>> >
>> > The result was that it was more likely an I2C transport bug than a
>> > hid-multitouch one (see comment #8 in the fdo bug).
>> >
>> > You can try to run hid-recorder when you see the problems, and then
>> > parse the output (or just send it to me). There is huge chances that
>> > there will be no events from I2C sending the release.
>> >
>> > And again, I am not sure how we could end up debugging this in the
>> > i2c-designware driver :(
>> >
>>
>> Does this ring a bell?
>
> i2c-designware usually prints errors to dmesg if it fails to transfer
> messages. Can you include dmesg of the failure as well?
Nothing shows up at all. All I have is:
input: DLL0704:01 06CB:76AE Touchpad as
/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-17 18:43 ` Andy Lutomirski
@ 2016-03-17 20:24 ` Andrew Duggan
2016-03-18 17:42 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Andrew Duggan @ 2016-03-17 20:24 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>> [add i2c-designware maintainers]
>>>
>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>> > Hi Andy,
>>> >
>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>> >> Hi-
>>> >>
>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>> >> had this issue in 4.4.
>>> >>
>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>> >> by pressing three fingers down in sequence and then releasing them.
>>> >> After doing that, left-clicks worked.
>>> >
>>> > I think I already have been reported the issue here:
>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>> >
>>> > The result was that it was more likely an I2C transport bug than a
>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>> >
>>> > You can try to run hid-recorder when you see the problems, and then
>>> > parse the output (or just send it to me). There is huge chances that
>>> > there will be no events from I2C sending the release.
>>> >
>>> > And again, I am not sure how we could end up debugging this in the
>>> > i2c-designware driver :(
>>> >
>>>
>>> Does this ring a bell?
>>
>> i2c-designware usually prints errors to dmesg if it fails to transfer
>> messages. Can you include dmesg of the failure as well?
>
> Nothing shows up at all. All I have is:
>
> input: DLL0704:01 06CB:76AE Touchpad as
> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
What is the fw id? I have a 9343 with the same touchpad and have not
noticed an issue. This is the dmesg output for my touchpad.
[ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
id: 1832324
If we have the same firmware version then we can eliminate that as a factor.
> --
> 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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-17 20:24 ` Andrew Duggan
@ 2016-03-18 17:42 ` Andy Lutomirski
2016-03-18 18:53 ` Andrew Duggan
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-03-18 17:42 UTC (permalink / raw)
To: Andrew Duggan
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
>> <mika.westerberg@linux.intel.com> wrote:
>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>>> [add i2c-designware maintainers]
>>>>
>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>>> > Hi Andy,
>>>> >
>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>>> >> Hi-
>>>> >>
>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>>> >> had this issue in 4.4.
>>>> >>
>>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>>> >> by pressing three fingers down in sequence and then releasing them.
>>>> >> After doing that, left-clicks worked.
>>>> >
>>>> > I think I already have been reported the issue here:
>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>>> >
>>>> > The result was that it was more likely an I2C transport bug than a
>>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>>> >
>>>> > You can try to run hid-recorder when you see the problems, and then
>>>> > parse the output (or just send it to me). There is huge chances that
>>>> > there will be no events from I2C sending the release.
>>>> >
>>>> > And again, I am not sure how we could end up debugging this in the
>>>> > i2c-designware driver :(
>>>> >
>>>>
>>>> Does this ring a bell?
>>>
>>> i2c-designware usually prints errors to dmesg if it fails to transfer
>>> messages. Can you include dmesg of the failure as well?
>>
>> Nothing shows up at all. All I have is:
>>
>> input: DLL0704:01 06CB:76AE Touchpad as
>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
>
> What is the fw id? I have a 9343 with the same touchpad and have not
> noticed an issue. This is the dmesg output for my touchpad.
>
> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
> id: 1832324
Mine is shinier and newer, apparently.
psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-18 17:42 ` Andy Lutomirski
@ 2016-03-18 18:53 ` Andrew Duggan
2016-04-22 16:37 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Andrew Duggan @ 2016-03-18 18:53 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
On Fri, Mar 18, 2016 at 10:42 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
>>> <mika.westerberg@linux.intel.com> wrote:
>>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>>>> [add i2c-designware maintainers]
>>>>>
>>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>>>> > Hi Andy,
>>>>> >
>>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>>>> >> Hi-
>>>>> >>
>>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>>>> >> had this issue in 4.4.
>>>>> >>
>>>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>>>> >> by pressing three fingers down in sequence and then releasing them.
>>>>> >> After doing that, left-clicks worked.
>>>>> >
>>>>> > I think I already have been reported the issue here:
>>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>>>> >
>>>>> > The result was that it was more likely an I2C transport bug than a
>>>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>>>> >
>>>>> > You can try to run hid-recorder when you see the problems, and then
>>>>> > parse the output (or just send it to me). There is huge chances that
>>>>> > there will be no events from I2C sending the release.
>>>>> >
>>>>> > And again, I am not sure how we could end up debugging this in the
>>>>> > i2c-designware driver :(
>>>>> >
>>>>>
>>>>> Does this ring a bell?
>>>>
>>>> i2c-designware usually prints errors to dmesg if it fails to transfer
>>>> messages. Can you include dmesg of the failure as well?
>>>
>>> Nothing shows up at all. All I have is:
>>>
>>> input: DLL0704:01 06CB:76AE Touchpad as
>>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
>>
>> What is the fw id? I have a 9343 with the same touchpad and have not
>> noticed an issue. This is the dmesg output for my touchpad.
>>
>> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
>> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
>> id: 1832324
>
> Mine is shinier and newer, apparently.
>
> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
> caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
It looks like you actually have a slightly newer revision of the
module (76AE vs my 76AD). So I can't quite do a direct comparison.
However, the 9350 system listed in the bug does have my exact module.
Which is why we think it might be a problem with the embedded I2C
chipset in the 9350.
Andrew
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-03-18 18:53 ` Andrew Duggan
@ 2016-04-22 16:37 ` Andy Lutomirski
2016-06-26 23:37 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-04-22 16:37 UTC (permalink / raw)
To: Andrew Duggan, Mario Limonciello
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
Adding Mario.
On Fri, Mar 18, 2016 at 11:53 AM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
> On Fri, Mar 18, 2016 at 10:42 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>> On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>>> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
>>>> <mika.westerberg@linux.intel.com> wrote:
>>>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>>>>> [add i2c-designware maintainers]
>>>>>>
>>>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>>>>> > Hi Andy,
>>>>>> >
>>>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>>>>> >> Hi-
>>>>>> >>
>>>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>>>>> >> had this issue in 4.4.
>>>>>> >>
>>>>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>>>>> >> by pressing three fingers down in sequence and then releasing them.
>>>>>> >> After doing that, left-clicks worked.
>>>>>> >
>>>>>> > I think I already have been reported the issue here:
>>>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>>>>> >
>>>>>> > The result was that it was more likely an I2C transport bug than a
>>>>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>>>>> >
>>>>>> > You can try to run hid-recorder when you see the problems, and then
>>>>>> > parse the output (or just send it to me). There is huge chances that
>>>>>> > there will be no events from I2C sending the release.
>>>>>> >
>>>>>> > And again, I am not sure how we could end up debugging this in the
>>>>>> > i2c-designware driver :(
>>>>>> >
>>>>>>
>>>>>> Does this ring a bell?
>>>>>
>>>>> i2c-designware usually prints errors to dmesg if it fails to transfer
>>>>> messages. Can you include dmesg of the failure as well?
>>>>
>>>> Nothing shows up at all. All I have is:
>>>>
>>>> input: DLL0704:01 06CB:76AE Touchpad as
>>>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
>>>
>>> What is the fw id? I have a 9343 with the same touchpad and have not
>>> noticed an issue. This is the dmesg output for my touchpad.
>>>
>>> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
>>> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
>>> id: 1832324
>>
>> Mine is shinier and newer, apparently.
>>
>> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
>> caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
>
> It looks like you actually have a slightly newer revision of the
> module (76AE vs my 76AD). So I can't quite do a direct comparison.
> However, the 9350 system listed in the bug does have my exact module.
> Which is why we think it might be a problem with the embedded I2C
> chipset in the 9350.
>
> Andrew
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-04-22 16:37 ` Andy Lutomirski
@ 2016-06-26 23:37 ` Andy Lutomirski
2016-06-27 4:11 ` Andy Lutomirski
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-06-26 23:37 UTC (permalink / raw)
To: Andrew Duggan, Mario Limonciello
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
On Fri, Apr 22, 2016 at 9:37 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> Adding Mario.
>
> On Fri, Mar 18, 2016 at 11:53 AM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>> On Fri, Mar 18, 2016 at 10:42 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>> On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>>>> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>>>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
>>>>> <mika.westerberg@linux.intel.com> wrote:
>>>>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>>>>>> [add i2c-designware maintainers]
>>>>>>>
>>>>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>>>>>> > Hi Andy,
>>>>>>> >
>>>>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>>>>>> >> Hi-
>>>>>>> >>
>>>>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>>>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>>>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>>>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>>>>>> >> had this issue in 4.4.
>>>>>>> >>
>>>>>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>>>>>> >> by pressing three fingers down in sequence and then releasing them.
>>>>>>> >> After doing that, left-clicks worked.
>>>>>>> >
>>>>>>> > I think I already have been reported the issue here:
>>>>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>>>>>> >
>>>>>>> > The result was that it was more likely an I2C transport bug than a
>>>>>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>>>>>> >
>>>>>>> > You can try to run hid-recorder when you see the problems, and then
>>>>>>> > parse the output (or just send it to me). There is huge chances that
>>>>>>> > there will be no events from I2C sending the release.
>>>>>>> >
>>>>>>> > And again, I am not sure how we could end up debugging this in the
>>>>>>> > i2c-designware driver :(
>>>>>>> >
>>>>>>>
>>>>>>> Does this ring a bell?
>>>>>>
>>>>>> i2c-designware usually prints errors to dmesg if it fails to transfer
>>>>>> messages. Can you include dmesg of the failure as well?
>>>>>
>>>>> Nothing shows up at all. All I have is:
>>>>>
>>>>> input: DLL0704:01 06CB:76AE Touchpad as
>>>>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
>>>>
>>>> What is the fw id? I have a 9343 with the same touchpad and have not
>>>> noticed an issue. This is the dmesg output for my touchpad.
>>>>
>>>> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
>>>> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
>>>> id: 1832324
>>>
>>> Mine is shinier and newer, apparently.
>>>
>>> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
>>> caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
>>
>> It looks like you actually have a slightly newer revision of the
>> module (76AE vs my 76AD). So I can't quite do a direct comparison.
>> However, the 9350 system listed in the bug does have my exact module.
>> Which is why we think it might be a problem with the embedded I2C
>> chipset in the 9350.
I don't know if this was a change in Fedora 24 or a change in the BIOS
1.4.3, but this problem has gotten *much* worse. It seems to trigger
every 30 seconds or so for me now.
--Andy
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-06-26 23:37 ` Andy Lutomirski
@ 2016-06-27 4:11 ` Andy Lutomirski
2016-06-27 7:47 ` Benjamin Tissoires
0 siblings, 1 reply; 12+ messages in thread
From: Andy Lutomirski @ 2016-06-27 4:11 UTC (permalink / raw)
To: Andrew Duggan, Mario Limonciello
Cc: Mika Westerberg, Benjamin Tissoires, linux-input, Jiri Kosina,
Jingoo Han, Pratyush Anand
[-- Attachment #1: Type: text/plain, Size: 4123 bytes --]
On Sun, Jun 26, 2016 at 4:37 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> On Fri, Apr 22, 2016 at 9:37 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>> Adding Mario.
>>
>> On Fri, Mar 18, 2016 at 11:53 AM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>>> On Fri, Mar 18, 2016 at 10:42 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
>>>>> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>>>>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
>>>>>> <mika.westerberg@linux.intel.com> wrote:
>>>>>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
>>>>>>>> [add i2c-designware maintainers]
>>>>>>>>
>>>>>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
>>>>>>>> > Hi Andy,
>>>>>>>> >
>>>>>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
>>>>>>>> >> Hi-
>>>>>>>> >>
>>>>>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
>>>>>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
>>>>>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
>>>>>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
>>>>>>>> >> had this issue in 4.4.
>>>>>>>> >>
>>>>>>>> >> I've attached what I think is an evtest issue of my fixing the issue
>>>>>>>> >> by pressing three fingers down in sequence and then releasing them.
>>>>>>>> >> After doing that, left-clicks worked.
>>>>>>>> >
>>>>>>>> > I think I already have been reported the issue here:
>>>>>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
>>>>>>>> >
>>>>>>>> > The result was that it was more likely an I2C transport bug than a
>>>>>>>> > hid-multitouch one (see comment #8 in the fdo bug).
>>>>>>>> >
>>>>>>>> > You can try to run hid-recorder when you see the problems, and then
>>>>>>>> > parse the output (or just send it to me). There is huge chances that
>>>>>>>> > there will be no events from I2C sending the release.
>>>>>>>> >
>>>>>>>> > And again, I am not sure how we could end up debugging this in the
>>>>>>>> > i2c-designware driver :(
>>>>>>>> >
>>>>>>>>
>>>>>>>> Does this ring a bell?
>>>>>>>
>>>>>>> i2c-designware usually prints errors to dmesg if it fails to transfer
>>>>>>> messages. Can you include dmesg of the failure as well?
>>>>>>
>>>>>> Nothing shows up at all. All I have is:
>>>>>>
>>>>>> input: DLL0704:01 06CB:76AE Touchpad as
>>>>>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
>>>>>
>>>>> What is the fw id? I have a 9343 with the same touchpad and have not
>>>>> noticed an issue. This is the dmesg output for my touchpad.
>>>>>
>>>>> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
>>>>> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
>>>>> id: 1832324
>>>>
>>>> Mine is shinier and newer, apparently.
>>>>
>>>> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
>>>> caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
>>>
>>> It looks like you actually have a slightly newer revision of the
>>> module (76AE vs my 76AD). So I can't quite do a direct comparison.
>>> However, the 9350 system listed in the bug does have my exact module.
>>> Which is why we think it might be a problem with the embedded I2C
>>> chipset in the 9350.
>
> I don't know if this was a change in Fedora 24 or a change in the BIOS
> 1.4.3, but this problem has gotten *much* worse. It seems to trigger
> every 30 seconds or so for me now.
>
After fiddling for a bit, this seems to be somehow related to palm
detection or typing detection. I can't seem to trigger it with just
pointer movements, but if I type (with my palms necessarily near the
touchpad), it triggers quickly.
hid-recorder output attached. I don't know how to decode it sort of
playing it back with hid-replay, and that doesn't seem terribly
helpful. It's plausible that this is a userspace bug, and the
hid-recorder output should make it clear either way.
--Andy
[-- Attachment #2: hidrec.txt.xz --]
[-- Type: application/x-xz, Size: 25424 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: hid-multitouch stuck taps, possibly 4.5 regression?
2016-06-27 4:11 ` Andy Lutomirski
@ 2016-06-27 7:47 ` Benjamin Tissoires
0 siblings, 0 replies; 12+ messages in thread
From: Benjamin Tissoires @ 2016-06-27 7:47 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Andrew Duggan, Mario Limonciello, Mika Westerberg, linux-input,
Jiri Kosina, Jingoo Han, Pratyush Anand
On Jun 26 2016 or thereabouts, Andy Lutomirski wrote:
> On Sun, Jun 26, 2016 at 4:37 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> > On Fri, Apr 22, 2016 at 9:37 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >> Adding Mario.
> >>
> >> On Fri, Mar 18, 2016 at 11:53 AM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
> >>> On Fri, Mar 18, 2016 at 10:42 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >>>> On Thu, Mar 17, 2016 at 1:24 PM, Andrew Duggan <andrew.duggan@gmail.com> wrote:
> >>>>> On Thu, Mar 17, 2016 at 11:43 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >>>>>> On Thu, Mar 17, 2016 at 1:06 AM, Mika Westerberg
> >>>>>> <mika.westerberg@linux.intel.com> wrote:
> >>>>>>> On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
> >>>>>>>> [add i2c-designware maintainers]
> >>>>>>>>
> >>>>>>>> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
> >>>>>>>> > Hi Andy,
> >>>>>>>> >
> >>>>>>>> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
> >>>>>>>> >> Hi-
> >>>>>>>> >>
> >>>>>>>> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
> >>>>>>>> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
> >>>>>>>> >> ends up middle-clicking. I think it's a kernel issue and not a
> >>>>>>>> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
> >>>>>>>> >> had this issue in 4.4.
> >>>>>>>> >>
> >>>>>>>> >> I've attached what I think is an evtest issue of my fixing the issue
> >>>>>>>> >> by pressing three fingers down in sequence and then releasing them.
> >>>>>>>> >> After doing that, left-clicks worked.
> >>>>>>>> >
> >>>>>>>> > I think I already have been reported the issue here:
> >>>>>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
> >>>>>>>> >
> >>>>>>>> > The result was that it was more likely an I2C transport bug than a
> >>>>>>>> > hid-multitouch one (see comment #8 in the fdo bug).
> >>>>>>>> >
> >>>>>>>> > You can try to run hid-recorder when you see the problems, and then
> >>>>>>>> > parse the output (or just send it to me). There is huge chances that
> >>>>>>>> > there will be no events from I2C sending the release.
> >>>>>>>> >
> >>>>>>>> > And again, I am not sure how we could end up debugging this in the
> >>>>>>>> > i2c-designware driver :(
> >>>>>>>> >
> >>>>>>>>
> >>>>>>>> Does this ring a bell?
> >>>>>>>
> >>>>>>> i2c-designware usually prints errors to dmesg if it fails to transfer
> >>>>>>> messages. Can you include dmesg of the failure as well?
> >>>>>>
> >>>>>> Nothing shows up at all. All I have is:
> >>>>>>
> >>>>>> input: DLL0704:01 06CB:76AE Touchpad as
> >>>>>> /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-7/i2c-DLL0704:01/0018:06CB:76AE.0001/input/input12
> >>>>>
> >>>>> What is the fw id? I have a 9343 with the same touchpad and have not
> >>>>> noticed an issue. This is the dmesg output for my touchpad.
> >>>>>
> >>>>> [ 5.216319] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
> >>>>> id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 3038, fw
> >>>>> id: 1832324
> >>>>
> >>>> Mine is shinier and newer, apparently.
> >>>>
> >>>> psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1,
> >>>> caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3038, fw id: 2011643
> >>>
> >>> It looks like you actually have a slightly newer revision of the
> >>> module (76AE vs my 76AD). So I can't quite do a direct comparison.
> >>> However, the 9350 system listed in the bug does have my exact module.
> >>> Which is why we think it might be a problem with the embedded I2C
> >>> chipset in the 9350.
> >
> > I don't know if this was a change in Fedora 24 or a change in the BIOS
> > 1.4.3, but this problem has gotten *much* worse. It seems to trigger
> > every 30 seconds or so for me now.
> >
It's actually a change in both. The new bios fixes some issues but also
changed the firmware were the palm detection patch you mention below is
screwing things up.
>
> After fiddling for a bit, this seems to be somehow related to palm
> detection or typing detection. I can't seem to trigger it with just
> pointer movements, but if I type (with my palms necessarily near the
> touchpad), it triggers quickly.
>
> hid-recorder output attached. I don't know how to decode it sort of
> playing it back with hid-replay, and that doesn't seem terribly
> helpful. It's plausible that this is a userspace bug, and the
> hid-recorder output should make it clear either way.
Allen Hung submitted a fix for that:
http://www.spinics.net/lists/linux-input/msg45375.html
http://www.spinics.net/lists/linux-input/msg45376.html
I still need to review it, but I was sick last Thu/Fri and couldn't get
anything done properly.
Cheers,
Benjamin
>
> --Andy
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2016-06-27 7:47 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-15 21:47 hid-multitouch stuck taps, possibly 4.5 regression? Andy Lutomirski
2016-03-16 8:47 ` Benjamin Tissoires
2016-03-16 21:59 ` Andy Lutomirski
2016-03-17 8:06 ` Mika Westerberg
2016-03-17 18:43 ` Andy Lutomirski
2016-03-17 20:24 ` Andrew Duggan
2016-03-18 17:42 ` Andy Lutomirski
2016-03-18 18:53 ` Andrew Duggan
2016-04-22 16:37 ` Andy Lutomirski
2016-06-26 23:37 ` Andy Lutomirski
2016-06-27 4:11 ` Andy Lutomirski
2016-06-27 7:47 ` Benjamin Tissoires
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.