From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Filipe Laíns" <lains@riseup.net>,
"Bastien Nocera" <hadess@hadess.net>,
"Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>
Cc: Linux Input Devices <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
guy.b@bluewin.ch, poncho@spahan.ch,
Bastien Nocera <hadess@hadess.net>
Subject: Re: [regression] Since kernel 6.3.1 logitech unify receiver not working properly
Date: Wed, 17 May 2023 20:17:02 +0700 [thread overview]
Message-ID: <ZGTTznb+zal7XRkv@debian.me> (raw)
In-Reply-To: <bec024d5-4088-00ae-f7b5-7188868b1707@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Thu, May 11, 2023 at 01:58:43PM +0200, Thorsten Leemhuis wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> On 08.05.23 11:55, Linux regression tracking (Thorsten Leemhuis) wrote:
> > Hi, Thorsten here, the Linux kernel's regression tracker.
> >
> > I noticed a regression report in bugzilla.kernel.org. As many (most?)
> > kernel developers don't keep an eye on it, I decided to forward it by mail.
> >
> > Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217412 :
>
> TWIMC: a few other users (three or four iirc) showed up in that ticket
> and reported problems with the receiver, albeit the symptoms are not
> exactly the same for all of them, so there might be more than one problem.
>
> I'll try to motivate the affected users to perform a bisection. But
> would be great if those with more knowledge about this code could
> briefly look into the ticket, maybe the details the users shared allows
> one of you to guess what causes this.
Hi Thorsten,
Another reporter in the same bug ticket has already pinned down the
culprit to 586e8fede7953b ("HID: logitech-hidpp: Retry commands when device
is busy"). I'm now updating regzbot entry (and Cc'ing the culprit author):
#regzbot introduced: 586e8fede7953b
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-05-17 13:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 9:55 [regression] Since kernel 6.3.1 logitech unify receiver not working properly Linux regression tracking (Thorsten Leemhuis)
2023-05-11 11:58 ` Thorsten Leemhuis
2023-05-16 13:24 ` Bagas Sanjaya
2023-05-16 13:34 ` Benjamin Tissoires
2023-05-22 12:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 18:23 ` Linus Torvalds
2023-05-23 12:31 ` Jiri Kosina
2023-05-24 15:27 ` Benjamin Tissoires
2023-05-25 11:10 ` Jiri Kosina
2023-05-25 11:19 ` Benjamin Tissoires
2023-05-26 18:41 ` Jiri Kosina
2023-05-28 12:21 ` Thorsten Leemhuis
2023-05-31 8:43 ` Jiri Kosina
2023-05-31 8:46 ` Bastien Nocera
2023-05-16 13:53 ` Thorsten Leemhuis
2023-05-17 13:17 ` Bagas Sanjaya [this message]
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=ZGTTznb+zal7XRkv@debian.me \
--to=bagasdotme@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=guy.b@bluewin.ch \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poncho@spahan.ch \
--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;
as well as URLs for NNTP newsgroup(s).