From: Mark Lord <mlord@pobox.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Jiri Kosina <jikos@kernel.org>,
Bastien Nocera <hadess@hadess.net>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Peter F . Patel-Schneider" <pfpschneider@gmail.com>,
"Filipe Laíns" <lains@riseup.net>,
"Nestor Lopez Casado" <nlopezcasad@logitech.com>
Subject: Re: [PATCH] HID: logitech-hidpp: Handle timeout differently from busy
Date: Thu, 15 Jun 2023 07:24:15 -0400 [thread overview]
Message-ID: <aa0e3371-dad1-3296-18fb-1957b92aa4d1@pobox.com> (raw)
In-Reply-To: <53903462-2552-b707-3831-cad3ef873b0d@leemhuis.info>
On 2023-06-15 03:24 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
>
...
> https://bugzilla.kernel.org/show_bug.cgi?id=217412
>
> --- Comment #47 from Mark Blakeney ---
> @Juha, kernel 6.3.7 adds the 2 patches intended to fix this bug and the
> startup delay is now gone. However, I have had 2 cases over the last 5
> days in which I have been running 6.3.7 where my mouse fails to be
> detected at all after startup. I have to pull the Logitech receiver
> out/in to get the mouse working. Never seen this issue before so I
> suspect the patches are not right.
> ```
I too have had that happen with recent kernels, but have not yet put
a finger to a specific version or cause.
Just toggling the power button on the wireless mouse is enough for
it to "re-appear".
The 5.4.xx kernels never had this issue. I went straight from those
to the 6.3.xx ones, where it does happen sometimes, both with and without
the recent "delay" fixes.
--
Mark Lord
next prev parent reply other threads:[~2023-06-15 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 8:24 Bastien Nocera
2023-05-31 14:07 ` Jiri Kosina
2023-06-03 12:41 ` Jiri Kosina
2023-06-03 13:17 ` Mark Lord
2023-06-05 14:20 ` Benjamin Tissoires
2023-06-05 14:31 ` Mark Lord
2023-06-05 8:44 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 14:27 ` Benjamin Tissoires
2023-06-05 16:25 ` Mark Lord
2023-06-05 17:04 ` Benjamin Tissoires
2023-06-05 17:47 ` Mark Lord
2023-06-05 20:03 ` Jiri Kosina
2023-06-06 13:27 ` Jiri Kosina
2023-06-06 18:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-06 18:37 ` Benjamin Tissoires
2023-06-07 9:46 ` Greg Kroah-Hartman
2023-06-07 10:07 ` Benjamin Tissoires
2023-06-15 7:24 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-15 11:24 ` Mark Lord [this message]
2023-06-21 14:03 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-21 15:10 ` Benjamin Tissoires
2023-06-21 17:19 ` Linux regression tracking (Thorsten Leemhuis)
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=aa0e3371-dad1-3296-18fb-1957b92aa4d1@pobox.com \
--to=mlord@pobox.com \
--cc=benjamin.tissoires@redhat.com \
--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=nlopezcasad@logitech.com \
--cc=pfpschneider@gmail.com \
--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®