[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e10112a-7560-4dd8-8a03-5fdfc838168f@leemhuis.info>
Date: Tue, 21 Nov 2023 14:53:17 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Input Devices <linux-input@...r.kernel.org>
Cc: Mavroudis Chatzilazaridis <mavchatz@...tonmail.com>,
Filipe LaĆns <lains@...eup.net>,
Bastien Nocera <hadess@...ess.net>,
Jiri Kosina <jkosina@...e.cz>,
LinuxCat <masch77.linuxcat@...il.com>,
Marcelo <mmbossoni@...il.com>, Takashi Iwai <tiwai@...e.de>,
Hans de Goede <hdegoede@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Benjamin Tissoires <benjamin.tissoires@...hat.com>
Subject: Re: Fwd: Logitech G915 Wireless Keyboard acts weird on 6.6.0
On 21.11.23 14:09, Bagas Sanjaya wrote:
> On Thu, Nov 02, 2023 at 09:11:42PM +0700, Bagas Sanjaya wrote:
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>
>>> Hello, After upgrading from 6.5.9 to 6.6.0, my keyboard started
>>> acting really weird in its wireless mode, key actions sent are
>>> completely wrong, see video attached.
>>>
>>> Most keys are perceived as either E, 3 or F7, with F8 and <, as
>>> well.
> [...]
>>> 9d1bd9346241cd6963b58da7ffb7ed303285f684 is the first bad commit
>>> commit 9d1bd9346241cd6963b58da7ffb7ed303285f684 Author: Mavroudis
>>> Chatzilazaridis <mavchatz@...tonmail.com> Date: Sun Jul 16
>>> 18:23:44 2023 +0000
>>>
>>> HID: logitech-dj: Add support for a new lightspeed receiver
>>> iteration
> [...]
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=218094
>
> There's no reply from culprit author nor linux-input people (did they
> miss this regression?).
I guess part of the problem is that Bastien got reassigned and might not
care about the kernel anymore.
Another part of it is that Jiri was CCed, but Benjamin was not.
Ideally of course Mavroudis Chatzilazaridis, the culprit's author would
look into this, but from a quick search on lore it looks like Mavroudis
is not a regular kernel contributor and thus might not even know how we
expect situations like this to be handled.
> And on Bugzilla, other reporters replied that
> reverting the culprit fixed the regression.
>From Takashi's comments like
https://bugzilla.kernel.org/show_bug.cgi?id=218094#c33 it sounds like
this can be fixed by resolving another regression as discussed earlier
today here:
https://lore.kernel.org/all/87edgjo2kr.wl-tiwai@suse.de/
I think that might be the better solution, but Takashi, Hans, or the
input people will know best.
> FYI, there's similar Bugzilla report on [1].
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=218172
Not sure, that might be a different problem, guess Hans is the best to
judge.
> Also Cc'ed Linus.
Linus can speak for himself, but I guess he gets enough mail already.
I'd say in a situation like this it thus might best to not CC him;
instead poke me when things apparently are not handled well, then we
together can decide if it's worth bringing Linus in.
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