lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ziofbee4q5cvxvovpzb2rfjw2cduefpm4umwtfyyx5kfwajjp4@nrjwkqryz2j5>
Date: Sat, 23 Nov 2024 17:42:06 +0100
From: Benjamin Tissoires <bentiss@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jiri Kosina <jikos@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] HID for 6.13

On Nov 22 2024, Linus Torvalds wrote:
> On Mon, 18 Nov 2024 at 13:16, Jiri Kosina <jikos@...nel.org> wrote:
> >
> > please pull from
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git tags/hid-for-linus-2024111801
> >
> > to receive HID subsystem queue for 6.13 merge window.
> 
> Hmm. There's something odd going on here. My mouse scroll-wheel
> stopped working (Logitech MX Anywhere 3), and this pull would look
> like the prime suspect.
> 
> The mouse otherwise works, so it's not that the mouse isn't found,
> it's literally just the scroll-wheel functionality that doesn't work.
> 
> Oddly enough, if I remove and re-insert the Logitech wireless dongle,
> the scroll wheel works again. So it's not some kind of complete
> breakage - but it also wasn't a one-time fluke thing, in that it
> happened twice in a row when rebooting into a new kernel.
> 
> Any ideas? Does this make anybody go "Hmm, maybe ..."
> 

IMO the suspect might be 526748b925185e95f1415900ee13c2469d4b64cc.

My idea is that if you reboot without completely stopping the pc the
mouse stays connected in the "high res" wheel mode which hid-multitouch
can not handle. However I don't think the bolt receiver is supported in
either hid-logitech-dj.ko nor hid-logitech-hidpp.ko.

In addition to Jiri's requests, could you also post the dmesg after the
fresh (and broken) reboot, and after unplug/replug the dongle? We would
get more information on to which kernel modules are involved this way.

Cheers,
Benjamin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ