Hi, On 2/28/23 14:26, Benjamin Tissoires wrote: > On Tue, Feb 28, 2023 at 12:32 PM Thorsten Leemhuis > <regressions@xxxxxxxxxxxxx> wrote: >> >> On 19.01.23 16:06, Linux kernel regression tracking (Thorsten Leemhuis) >> wrote: >>> Hi, this is your Linux kernel regression tracker. >>> >>> I noticed a regression report in bugzilla.kernel.org. As many (most?) >>> kernel developer don't keep an eye on it, I decided to forward it by >>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216946 : >> >> The reporter recently confirmed in the ticket that the issue still >> happens with 6.2. >> >> There wasn't any reply from any of the input developers here or in >> bugzilla afaics. :-/ Hmmm. Could someone from that camp maybe please >> take a minute and at least briefly look into this as answer something >> like "that might be due to a problem in subsystem 'foo'", "maybe ask bar >> for an option", or "we have no idea what might cause this, this needs to >> be bisected"? That would help a lot. > > The working dmesg shows a line with: > hid-generic 0018:0457:10FB.0002: input,hidraw1: I2C HID v1.00 Device > [SIS0817:00 0457:10FB] on i2c-SIS0817:00 > and then > hid-multitouch 0018:0457:10FB.0002: input,hidraw1: I2C HID v1.00 > Device [SIS0817:00 0457:10FB] on i2c-SIS0817:00 > > But these 2 lines do not appear on the 6.1.4 logs. > > So the device is not properly enumerated by ACPI or I2C. Hans might > have an idea on how to debug/solve that issue. I actually have a Toshiba satellite click mini l9w-b lying around myself. I already made a note to try and reproduce this But I'm very much swamped with too much kernel work, so no promises when I will get around to this ... Regards, Hans >> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) >> -- >> Everything you wanna know about Linux kernel regression tracking: >> https://linux-regtracking.leemhuis.info/about/#tldr >> If I did something stupid, please tell me, as explained on that page. >> >> #regzbot poke >>>> Gé Koerkamp 2023-01-17 20:21:51 UTC >>>> >>>> Created attachment 303619 [details] >>>> Kernel configuration for v6.1.4/ journalctl (dmesg)/ ACPIdump/lsmod >>>> >>>> Overview: >>>> The touchscreen does not react on touch events. >>>> Touchscreen display and touchpad are working. >>>> >>>> Step to reproduce: >>>> Open any UI page >>>> Try to use touch on relevant UI controls (buttons etc.) >>>> >>>> Result: >>>> No reaction on screen touches >>>> >>>> Expected result: >>>> Reaction on touched control, same as when using the touch pad or connected mouse (which do work). >>>> >>>> Build information: >>>> The error happens with kernel version 6.1.4 >>>> After rebuilding with different kernel versions, it appears that it first fails with kernel 5.16 >>>> >>>> Additional builds: >>>> The click mini l9w-b still works with kernel 5.10.y LTS and 5.15.y LTS. >>>> >>>> Important remark: >>>> Touchscreen still works fine with kernel 6.1.4 using >>>> - an HP x2 detachable 10-p0xx or >>>> - a Lenovo yoga 520-14ikb >>>> >>>> So it could be a hardware dependent issue >>> >>> See the ticket for more details. >>> >>> >>> [TLDR for the rest of this mail: I'm adding this report to the list of >>> tracked Linux kernel regressions; the text you find below is based on a >>> few templates paragraphs you might have encountered already in similar >>> form.] >>> >>> BTW, let me use this mail to also add the report to the list of tracked >>> regressions to ensure it's doesn't fall through the cracks: >>> >>> #regzbot introduced: v5.15..v5.16 >>> https://bugzilla.kernel.org/show_bug.cgi?id=216946 >>> #regzbot title: hid: touchscreen broken with Toshiba satellite click >>> mini l9w-b >>> #regzbot ignore-activity >>> >>> This isn't a regression? This issue or a fix for it are already >>> discussed somewhere else? It was fixed already? You want to clarify when >>> the regression started to happen? Or point out I got the title or >>> something else totally wrong? Then just reply and tell me -- ideally >>> while also telling regzbot about it, as explained by the page listed in >>> the footer of this mail. >>> >>> Developers: When fixing the issue, remember to add 'Link:' tags pointing >>> to the report (e.g. the buzgzilla ticket and maybe this mail as well, if >>> this thread sees some discussion). See page linked in footer for details. >>> >>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) >>> -- >>> Everything you wanna know about Linux kernel regression tracking: >>> https://linux-regtracking.leemhuis.info/about/#tldr >>> If I did something stupid, please tell me, as explained on that page. >> >