mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gé Koerkamp" <ge.koerkamp@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216946 - Toshiba satellite click mini l9w-b: touchscreen: no touch events with kernel 6.1.4
Date: Tue, 28 Feb 2023 13:10:11 +0100	[thread overview]
Message-ID: <15A82C8F-324B-4E99-B388-27F1480B7959@gmail.com> (raw)
In-Reply-To: <abb495f7-f973-4614-846b-d3922dc0fe25@leemhuis.info>

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@leemhuis.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.

  reply	other threads:[~2023-02-28 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 15:06 Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-28 11:32 ` Thorsten Leemhuis
2023-02-28 12:10   ` Gé Koerkamp [this message]
2023-02-28 13:26   ` Benjamin Tissoires
2023-02-28 15:11     ` Linux regression tracking (Thorsten Leemhuis)
2023-03-01 11:41     ` Hans de Goede
2023-04-17 11:55       ` Linux regression tracking (Thorsten Leemhuis)
2023-04-19 16:21         ` Gé Koerkamp
2023-04-19 16:40           ` Hans de Goede
2023-04-20 11:17             ` Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15A82C8F-324B-4E99-B388-27F1480B7959@gmail.com \
    --to=ge.koerkamp@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®