FS#68178 - [linux] Touchscreen doesn't work anymore since linux 5.8.13/linux-lts 5.4.69

Attached to Project: Arch Linux
Opened by rainer (raneon) - Saturday, 10 October 2020, 12:36 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 09 February 2021, 08:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The touchscreen on the Matebook 12 doesn't work anymore after upgrading from linux 5.8.12 to 5.8.13/5.8.14. On linux-lts there is the same issue when upgrading from 5.4.68 to 5.4.69/5.4.70.

I've tried the touchscreen as well on a Dell XPS 13 9343 and there it works fine. So this seems related to the specific hardware driver.

Hardware:
- CPU Intel Core m3-6Y30
- GPU Intel Graphics 515
- Huawei Matebook 12


Additional info:
* linux 5.4.14
* linux-lts 5.4.70

Steps to reproduce:
1. Upgrade linux or linux-lts
2. Try touchscreen (tested in SDDM and KDE)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 09 February 2021, 08:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Upstream commit 8058d69905058ec8f467a120b5ec5bb831ea67f3 has been included into all stable kernel packages
Comment by freswa (frederik) - Saturday, 10 October 2020, 22:22 GMT
The best way to tackle this, would be to bisect the kernel between the releases and then send an email to the LKML to report the regression.
Comment by loqs (loqs) - Saturday, 10 October 2020, 22:41 GMT
Does the touchscreen use i2c? There were two i2c commits common to the mentioned stable updates
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.8.13&id=953fc770d069b167266d9d9ccfef0455fcfdc070
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.8.13&id=b7b5742eb70b2a168b43d5a2cbaf90bff18ae636

The first one seems much more likely to me. A full bisection though would not take much longer than testing reverting one commit and removes the guesswork.
Comment by rainer (raneon) - Monday, 12 October 2020, 12:28 GMT
I assume it is using i2c:

$ dmesg | grep i2c
[53817.549324] i2c_new_client_device+0x168/0x290
[53817.549331] i2c_new_device+0xa/0x20
[53817.549339] i2c_acpi_notify+0xd5/0x140
[53817.549371] i2c_acpi_install_space_handler+0x9d/0xd0
[53817.549378] i2c_register_adapter+0x1f6/0x3e0
[53817.549383] i2c_dw_probe+0x323/0x470
[53817.549389] dw_i2c_plat_probe+0x359/0x69a
[53837.619505] i2c_device_probe+0xb2/0x340
[53837.619557] i2c_new_client_device+0x168/0x290
[53837.619564] i2c_new_device+0xa/0x20
[53837.619572] i2c_acpi_notify+0xd5/0x140
[53837.619603] i2c_acpi_install_space_handler+0x9d/0xd0
[53837.619611] i2c_register_adapter+0x1f6/0x3e0
[53837.619616] i2c_dw_probe+0x323/0x470
[53837.619622] dw_i2c_plat_probe+0x359/0x69a
[54162.474302] i2c_device_probe+0xb2/0x340
[54162.474353] i2c_new_client_device+0x168/0x290
[54162.474360] i2c_new_device+0xa/0x20
[54162.474368] i2c_acpi_notify+0xd5/0x140
[54162.474400] i2c_acpi_install_space_handler+0x9d/0xd0
[54162.474407] i2c_register_adapter+0x1f6/0x3e0
[54162.474412] i2c_dw_probe+0x323/0x470
[54162.474418] dw_i2c_plat_probe+0x359/0x69a
[54182.534215] i2c_device_probe+0xb2/0x340
[54182.534266] i2c_new_client_device+0x168/0x290
[54182.534273] i2c_new_device+0xa/0x20
[54182.534281] i2c_acpi_notify+0xd5/0x140
[54182.534313] i2c_acpi_install_space_handler+0x9d/0xd0
[54182.534320] i2c_register_adapter+0x1f6/0x3e0
[54182.534325] i2c_dw_probe+0x323/0x470
[54182.534331] dw_i2c_plat_probe+0x359/0x69a
[54507.486155] i2c_device_probe+0xb2/0x340
[54507.486207] i2c_new_client_device+0x168/0x290
[54507.486213] i2c_new_device+0xa/0x20
[54507.486221] i2c_acpi_notify+0xd5/0x140
[54507.486253] i2c_acpi_install_space_handler+0x9d/0xd0
[54507.486260] i2c_register_adapter+0x1f6/0x3e0
[54507.486266] i2c_dw_probe+0x323/0x470
[54507.486271] dw_i2c_plat_probe+0x359/0x69a
[54527.561134] i2c_device_probe+0xb2/0x340
[54527.561185] i2c_new_client_device+0x168/0x290
[54527.561192] i2c_new_device+0xa/0x20
[54527.561200] i2c_acpi_notify+0xd5/0x140
[54527.561232] i2c_acpi_install_space_handler+0x9d/0xd0
[54527.561239] i2c_register_adapter+0x1f6/0x3e0
[54527.561244] i2c_dw_probe+0x323/0x470
[54527.561250] dw_i2c_plat_probe+0x359/0x69a
[54852.415894] i2c_device_probe+0xb2/0x340
[54852.415946] i2c_new_client_device+0x168/0x290
[54852.415952] i2c_new_device+0xa/0x20
[54852.415960] i2c_acpi_notify+0xd5/0x140
[54852.415992] i2c_acpi_install_space_handler+0x9d/0xd0
[54852.416000] i2c_register_adapter+0x1f6/0x3e0
[54852.416005] i2c_dw_probe+0x323/0x470
[54852.416011] dw_i2c_plat_probe+0x359/0x69a
[54872.486131] i2c_device_probe+0xb2/0x340
[54872.486183] i2c_new_client_device+0x168/0x290
[54872.486190] i2c_new_device+0xa/0x20
[54872.486198] i2c_acpi_notify+0xd5/0x140
[54872.486230] i2c_acpi_install_space_handler+0x9d/0xd0
[54872.486237] i2c_register_adapter+0x1f6/0x3e0
[54872.486242] i2c_dw_probe+0x323/0x470
[54872.486248] dw_i2c_plat_probe+0x359/0x69a
[55197.531514] i2c_device_probe+0xb2/0x340
[55197.531565] i2c_new_client_device+0x168/0x290
[55197.531572] i2c_new_device+0xa/0x20
[55197.531580] i2c_acpi_notify+0xd5/0x140
[55197.531611] i2c_acpi_install_space_handler+0x9d/0xd0
[55197.531618] i2c_register_adapter+0x1f6/0x3e0
[55197.531624] i2c_dw_probe+0x323/0x470
[55197.531629] dw_i2c_plat_probe+0x359/0x69a
[55217.606511] i2c_device_probe+0xb2/0x340
[55217.606563] i2c_new_client_device+0x168/0x290
[55217.606570] i2c_new_device+0xa/0x20
[55217.606578] i2c_acpi_notify+0xd5/0x140
[55217.606609] i2c_acpi_install_space_handler+0x9d/0xd0
[55217.606616] i2c_register_adapter+0x1f6/0x3e0
[55217.606621] i2c_dw_probe+0x323/0x470
[55217.606627] dw_i2c_plat_probe+0x359/0x69a
[55542.467709] i2c_device_probe+0xb2/0x340
[55542.467761] i2c_new_client_device+0x168/0x290
[55542.467768] i2c_new_device+0xa/0x20
[55542.467775] i2c_acpi_notify+0xd5/0x140
[55542.467807] i2c_acpi_install_space_handler+0x9d/0xd0
[55542.467815] i2c_register_adapter+0x1f6/0x3e0
[55542.467820] i2c_dw_probe+0x323/0x470
[55542.467826] dw_i2c_plat_probe+0x359/0x69a
[55562.555296] i2c_device_probe+0xb2/0x340
[55562.555348] i2c_new_client_device+0x168/0x290
[55562.555354] i2c_new_device+0xa/0x20
[55562.555362] i2c_acpi_notify+0xd5/0x140
[55562.555395] i2c_acpi_install_space_handler+0x9d/0xd0
[55562.555401] i2c_register_adapter+0x1f6/0x3e0
[55562.555407] i2c_dw_probe+0x323/0x470
[55562.555412] dw_i2c_plat_probe+0x359/0x69a
[55887.421479] i2c_device_probe+0xb2/0x340
[55887.421531] i2c_new_client_device+0x168/0x290
[55887.421538] i2c_new_device+0xa/0x20
[55887.421545] i2c_acpi_notify+0xd5/0x140
[55887.421577] i2c_acpi_install_space_handler+0x9d/0xd0
[55887.421584] i2c_register_adapter+0x1f6/0x3e0
[55887.421589] i2c_dw_probe+0x323/0x470
[55887.421595] dw_i2c_plat_probe+0x359/0x69a
[55907.491027] i2c_device_probe+0xb2/0x340
[55907.491079] i2c_new_client_device+0x168/0x290
[55907.491086] i2c_new_device+0xa/0x20
[55907.491094] i2c_acpi_notify+0xd5/0x140
[55907.491126] i2c_acpi_install_space_handler+0x9d/0xd0
[55907.491133] i2c_register_adapter+0x1f6/0x3e0
[55907.491138] i2c_dw_probe+0x323/0x470
[55907.491144] dw_i2c_plat_probe+0x359/0x69a

I've spent some time how to use git with bisect but I ended up just reverting the commit 21653a4181ff292480599dad996a2b759ccf050f. I've used and compiled linux-git from AUR.

This makes it possible to use my touchscreen again. Thank you for the help so far!

Do you know to whom I have to send now the bug report or do I need to open a ticket in the bugzilla? I've not done this before.

Comment by freswa (frederik) - Monday, 12 October 2020, 13:06 GMT
This stuff is handled on the linux-acpi mailing list. You can report this as a regression and you probably want to CC Hans de Goede <hdegoede@redhat.com>, Mika Westerberg <mika.westerberg@linux.intel.com> and Wolfram Sang <wsa@kernel.org>.
Comment by rainer (raneon) - Wednesday, 14 October 2020, 22:39 GMT
Seems like it will be fixed upstream soon. I've received a patch that worked for me.
   0001-i2c-core-Restore-acpi_wa... (2.4 KiB)
Comment by Hans de Goede (hansdegoede) - Thursday, 15 October 2020, 07:51 GMT
Sorry about this regression, as @raneon already mentioned a patch fixing this has been posted upstream and will hopefully be included upstream soon.

The fix (which raneon already attached) should be save to include as a downstream patch in the mean time, see here:

20201014144158.18036-1-hdegoede@redhat.com/"> https://lore.kernel.org/linux-i2c/20201014144158.18036-1-hdegoede@redhat.com/

For an explanation of the issue and why I believe this is a save fix to add.

Loading...