lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <15A82C8F-324B-4E99-B388-27F1480B7959@gmail.com>
Date:   Tue, 28 Feb 2023 13:10:11 +0100
From:   Gé Koerkamp <ge.koerkamp@...il.com>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>
Cc:     Jiri Kosina <jikos@...nel.org>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        "open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [regression] Bug 216946 - Toshiba satellite click mini l9w-b: touchscreen: no touch events with kernel 6.1.4

Hi,
additionally, I searched for any reported SIS0817 issues, yet did not find any.
But perhaps it rings a bell.
Cheers - Gé

On 28 Feb 2023, at 12:32, Thorsten Leemhuis <regressions@...mhuis.info> 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.

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ