Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   =?utf-8?Q?G=C3=A9_Koerkamp?= <ge.koerkamp@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: [regression] Bug 216946 - Toshiba satellite click mini l9w-b: touchscreen: no touch events with kernel 6.1.4
Date:   Wed, 19 Apr 2023 18:21:46 +0200
Message-Id: <E4123C4B-D6C0-4CB2-8328-E0D03599ED16@gmail.com>
References: <993dd537-2f74-3657-1dd3-c3a0a74e37e1@leemhuis.info>
Cc:     Hans de Goede <hdegoede@redhat.com>,
        Benjamin Tissoires <benjamin.tissoires@redhat.com>,
        Jiri Kosina <jikos@kernel.org>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        "open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <993dd537-2f74-3657-1dd3-c3a0a74e37e1@leemhuis.info>
To:     Linux regressions mailing list <regressions@lists.linux.dev>
Precedence: bulk

Hi Thorsten,

travelling at the moment, but I=E2=80=99ll try. Not really into bisecting ke=
rnel issues, but let=E2=80=99s see where this goes. Another issue is, that I=
 don=E2=80=99t have a Toshiba Mini Click myself, so I need to build the test=
 Volumio images (volumio.org) with the different 5.16-rc kernel patch versio=
ns for a colleague to work with, hopefully  he has time to do this.

Thanks - G=C3=A9

Sent from my iPhone

> On 17 Apr 2023, at 13:55, Linux regression tracking (Thorsten Leemhuis) <r=
egressions@leemhuis.info> wrote:
>=20
> =EF=BB=BF
>=20
>> On 01.03.23 12:41, Hans de Goede wrote:
>>> On 2/28/23 14:26, Benjamin Tissoires wrote:
>>> On Tue, Feb 28, 2023 at 12:32=E2=80=AFPM Thorsten Leemhuis
>>> <regressions@leemhuis.info> wrote:
>>>>=20
>>>> On 19.01.23 16:06, Linux kernel regression tracking (Thorsten Leemhuis)=

>>>> wrote:
>>>>> Hi, this is your Linux kernel regression tracker.
>>>>>=20
>>>>> 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=3D21694=
6 :
>>>>=20
>>>> The reporter recently confirmed in the ticket that the issue still
>>>> happens with 6.2.
>>>>=20
>>>> 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 ba=
r
>>>> for an option", or "we have no idea what might cause this, this needs t=
o
>>>> be bisected"? That would help a lot.
>>>=20
>>> 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
>>>=20
>>> But these 2 lines do not appear on the 6.1.4 logs.
>>>=20
>>> So the device is not properly enumerated by ACPI or I2C. Hans might
>>> have an idea on how to debug/solve that issue.
>>=20
>> I actually have a Toshiba satellite click mini l9w-b lying around
>> myself. I already made a note to try and reproduce this
>>=20
>> But I'm very much swamped with too much kernel work, so no promises
>> when I will get around to this ...
>=20
> Has anyone made any progress with this? Doesn't look like it, hence I
> wondered if this fall through the cracks; but maybe I'm just missing
> something.
>=20
> G=C3=A9 Koerkamp: with a bit of luck Hans sooner or later will have time t=
o
> look into this, but it might speed things up if you could try to bisect
> this.
>=20
> 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.
>=20
> #regzbot poke
>=20
>>>> 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.
>>>>=20
>>>> #regzbot poke
>>>>>> G=C3=A9 Koerkamp 2023-01-17 20:21:51 UTC
>>>>>>=20
>>>>>> Created attachment 303619 [details]
>>>>>> Kernel configuration for v6.1.4/ journalctl (dmesg)/ ACPIdump/lsmod
>>>>>>=20
>>>>>> Overview:
>>>>>> The touchscreen does not react on touch events.
>>>>>> Touchscreen display and touchpad are working.
>>>>>>=20
>>>>>> Step to reproduce:
>>>>>> Open any UI page
>>>>>> Try to use touch on relevant UI controls (buttons etc.)
>>>>>>=20
>>>>>> Result:
>>>>>> No reaction on screen touches
>>>>>>=20
>>>>>> Expected result:
>>>>>> Reaction on touched control, same as when using the touch pad or conn=
ected mouse (which do work).
>>>>>>=20
>>>>>> Build information:
>>>>>> The error happens with kernel version 6.1.4
>>>>>> After rebuilding with different kernel versions, it appears that it f=
irst fails with kernel 5.16
>>>>>>=20
>>>>>> Additional builds:
>>>>>> The click mini l9w-b still works with kernel 5.10.y LTS and 5.15.y LT=
S.
>>>>>>=20
>>>>>> Important remark:
>>>>>> Touchscreen still works fine with kernel 6.1.4 using
>>>>>> - an HP x2 detachable 10-p0xx or
>>>>>> - a Lenovo yoga 520-14ikb
>>>>>>=20
>>>>>> So it could be a hardware dependent issue
>>>>>=20
>>>>> See the ticket for more details.
>>>>>=20
>>>>>=20
>>>>> [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.]
>>>>>=20
>>>>> BTW, let me use this mail to also add the report to the list of tracke=
d
>>>>> regressions to ensure it's doesn't fall through the cracks:
>>>>>=20
>>>>> #regzbot introduced: v5.15..v5.16
>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=3D216946
>>>>> #regzbot title: hid: touchscreen broken with Toshiba satellite click
>>>>> mini l9w-b
>>>>> #regzbot ignore-activity
>>>>>=20
>>>>> 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 wh=
en
>>>>> 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 i=
n
>>>>> the footer of this mail.
>>>>>=20
>>>>> Developers: When fixing the issue, remember to add 'Link:' tags pointi=
ng
>>>>> to the report (e.g. the buzgzilla ticket and maybe this mail as well, i=
f
>>>>> this thread sees some discussion). See page linked in footer for detai=
ls.
>>>>>=20
>>>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' ha=
t)
>>>>> --
>>>>> 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.
>>>>=20
>>>=20
>>=20
>>=20
>>=20