Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65221 - Touchscreen of Surface Go stops working

Attached to Project: Arch Linux
Opened by Jan Ole Zabel (joz) - Monday, 20 January 2020, 16:43 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 21:55 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
The touchscreen in my Microsoft Surface Go stops accepting touch input whenever I upgrade the kernel to linux-5.4.13.
Pen input is also impossible.
It resumes to work when I downgrade to linux-5.4.11.

I tested Plasma and Gnome, and both are affected. Also downgrading of any other package except the kernel has no effect.

No additional log messages are generated, and the output of `libinput list-devices` does not change.
Touching the screen just has no effect anymore.

Additional info:
* linux 5.4.13.arch1-1 is affected
* Kernel params: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=/dev/mapper/crypt rootflags=compress=zstd,rw quiet splash
* libinput 1.15.0-1 is in use
* libgusb 0.3.2-2 is in use

Steps to reproduce:
Upgrade linux to linux-5.4.13.arch1-1.
This task depends upon

Closed by  freswa (frederik)
Thursday, 20 February 2020, 21:55 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://bugzilla.kernel.org/show_bug.cgi ?id=206259
Comment by Jan Ole Zabel (joz) - Monday, 20 January 2020, 21:15 GMT
Addition: `libinput debug-events` prints out touchscreen events only with the old kernel.
Comment by Michael B. (bofh1990) - Saturday, 25 January 2020, 13:52 GMT
Got the same Problem on my surface go running linux-5.4.14
Comment by alexander raban (alraban) - Saturday, 25 January 2020, 16:04 GMT
I can also confirm this bug in kernels >=5.4.13

There are also some errors in the journal >=5.4.13 which are not present on lower kernels, which appear to show the hid-multitouch driver failing:

Jan 25 10:54:20 [redacted] kernel: hid-multitouch 0018:04F3:261A.0007: report is too long
Jan 25 10:54:20 [redacted] kernel: hid-multitouch 0018:04F3:261A.0007: item 0 1 0 8 parsing failed
Comment by Jan Ole Zabel (joz) - Saturday, 25 January 2020, 16:42 GMT
Indeed, these are the differences of `journalctl -b -g multitouch` for me:

< Jan 25 13:14:41 archlinux kernel: hid-multitouch 0003:045E:096F.0004: input,hiddev2,hidraw3: USB HID v1.11 Mouse [Microsoft Surface Type Cover] on usb-0000:00:14.0-7/input3
< Jan 25 13:15:00 redacted kernel: hid-multitouch 0018:04F3:261A.0005: input,hidraw4: I2C HID v1.00 Device [ELAN9038:00 04F3:261A] on i2c-ELAN9038:00
---
> Jan 25 17:36:09 archlinux kernel: hid-multitouch 0003:045E:096F.0004: input,hiddev2,hidraw3: USB HID v1.11 Mouse [Microsoft Surface Type Cover] on usb-0000:00:14.0-7/input3
> Jan 25 17:36:26 redacted kernel: hid-multitouch 0018:04F3:261A.0005: report is too long
> Jan 25 17:36:26 redacted kernel: hid-multitouch 0018:04F3:261A.0005: item 0 1 0 8 parsing failed
> Jan 25 17:36:26 redacted kernel: hid-multitouch: probe of 0018:04F3:261A.0005 failed with error -22
Comment by Jan Ole Zabel (joz) - Saturday, 25 January 2020, 16:51 GMT
Seems very related to https://bugzilla.kernel.org/show_bug.cgi?id=206259

Loading...