All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux kernel regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Salvatore Bonaccorso <carnil@debian.org>,
	Tobias Klausmann <klausman@schwarzvogel.de>
Cc: linux-input@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Linux 6.1 and 6.2-rc make mousewheel on Logitech G903 (046d:c091) report too many non-hires events
Date: Sat, 28 Jan 2023 17:28:52 +0100	[thread overview]
Message-ID: <01fb3b37-8ba2-70f9-df62-4cf8df6bcc97@leemhuis.info> (raw)
In-Reply-To: <Y9VBz/GVZPqG3KwM@eldamar.lan>



On 28.01.23 16:39, Salvatore Bonaccorso wrote:
> On Wed, Jan 25, 2023 at 11:01:00PM +0100, Tobias Klausmann wrote:
>> Hi!
>>
>> As it says in the subject.
>>
>> At some point between 6.0 and 6.1, the kernel (if HID_LOGITECH_HIDPP was
>> m or y) started reporting a full event for every hires event on a
>> Logitech G903. 
>>
>> In my quest of finding out what the root cause is, ive filed these bugs:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029584
>> https://gitlab.freedesktop.org/libinput/libinput/-/issues/852
>>
>> The libinput one has the most detail. The most relevant one is this log
>> from libinput record, showing what happens if I turn the mousewheel by
>> one notch:
>>
>>     events:
>>     # Current time is 20:37:11
>>     - evdev:
>>       - [  3,  63476,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3,  63476,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3,  63476,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +3063ms
>>     - evdev:
>>       - [  3, 139476,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 139476,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 139476,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +76ms
>>     - evdev:
>>       - [  3, 197482,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 197482,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 197482,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +58ms
>>     - evdev:
>>       - [  3, 227485,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 227485,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 227485,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +30ms
>>     - evdev:
>>       - [  3, 240484,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 240484,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 240484,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +13ms
>>     - evdev:
>>       - [  3, 250470,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 250470,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 250470,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +10ms
>>     - evdev:
>>       - [  3, 256486,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 256486,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 256486,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +6ms
>>     - evdev:
>>       - [  3, 264472,   2,   8,      -1] # EV_REL / REL_WHEEL                -1
>>       - [  3, 264472,   2,  11,    -120] # EV_REL / REL_WHEEL_HI_RES       -120
>>       - [  3, 264472,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +8ms
>>     # Current time is 20:37:15
>>
>> Note how it reports both REL_WHEEL and REL_WHEEL_HI_RES at every
>> instance.
>>
>> I've tried assorted kernels, both Debian as well as hand-compiled
>> vanilla ones, and the problem only shows up if hid_logitech_hidpp.ko is
>> loaded, so I am blacklisting it for now. Also note that even unloading
>> the module didn't fix the behavior, though that may be because X11 was
>> still runing and so libinput's state ight have been still mangled.
>>
>> The most recent kernels I have tested with are 6.1.4 and 6.2-rc5.
>>
>> Best,
>> Tobias
> 
> Let's loop in as well the regresssions list.

Thx for that.

TWIMC, I assume it's the same issue as this one:
https://bugzilla.kernel.org/show_bug.cgi?id=216885

There in the past few days was some discussion about the issue with the
author of the culprit there.

HTH, 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-01-28 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 22:01 Linux 6.1 and 6.2-rc make mousewheel on Logitech G903 (046d:c091) report too many non-hires events Tobias Klausmann
2023-01-28 15:39 ` Salvatore Bonaccorso
2023-01-28 16:28   ` Linux kernel regression tracking (Thorsten Leemhuis) [this message]
2023-01-28 16:36     ` Tobias Klausmann
2023-02-02 12:21       ` Bastien Nocera
2023-02-16 14:53     ` Linux regression tracking #update (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=01fb3b37-8ba2-70f9-df62-4cf8df6bcc97@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=carnil@debian.org \
    --cc=klausman@schwarzvogel.de \
    --cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.