From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219789] [regression] Moving Logitech mouse causes WINE to lag
Date: Tue, 18 Feb 2025 09:26:21 +0000 [thread overview]
Message-ID: <bug-219789-208809-DBgUiAPGr6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219789-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219789
Esteve Varela Colominas (esteve.varela@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Esteve Varela Colominas (esteve.varela@gmail.com) ---
I've tried bisecting the issue, but was getting bogus results. On some reboots,
it would lag, but after rebooting again, it wouldn't lag at all.
After rebooting 6.6.67 a few times, this issue was reproducible there as well.
I'm under the impression that since 6.12, this issue has gotten worse, but I
cannot prove this appropriately. I've tried everything: downgrading microcode,
every in-between kernel version, disabling TLP, etc etc, and nothing seems to
make a difference.
The annoying bit is that I *know* it's a regression, but now I can't tell
what's causing it anymore. I don't play WINE games frequently enough to narrow
down when this happened.
Thanks, anyway.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-02-18 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 21:19 [Bug 219789] New: [regression] Moving Logitech mouse causes WINE to lag bugzilla-daemon
2025-02-18 9:26 ` bugzilla-daemon [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=bug-219789-208809-DBgUiAPGr6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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