I'm experiencing the issue with my Logitech M570 mouse since updating to
Ubuntu 24.04.2 LTS this morning. It does not affect my Logitech M187
mouse (travel/backup). Halp pleees
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2100565
Title:
kernel update broke Logitech G603 mouse over Bluetooth, other
Bluetooth devices work fine
Status in linux package in Ubuntu:
Confirmed
Bug description:
For the full story, see this Ubuntu Discourse thread:
https://discourse.ubuntu.com/t/recent-kernel-update-broke-
logitech-g603-mouse-over-bluetooth-other-bluetooth-devices-work-
fine/55707/1
Short summary of our findings:
On Ubuntu 24.04 LTS, between kernel 6.10.14 and 6.11-rc1, my Logitech
G603 mouse breaks in that while it is paired and connected, no mouse
clicks nor mouse movements are registered in 6.11-rc1 or later. The
problem exists all the way to the current RC, 6.14-rc4. I discovered
the bug firsthand when running a recent Ubuntu apt update that jumped
me from kernel 6.8.0-51 to 6.11.0-17.
Another user not using Ubuntu reports the same problem with his non-
Logitech Bluetooth keyboard and mouse. What we have in common is the
Intel Bluetooth adapter, which is "ID 8087:0aaa Intel Corp. Bluetooth
9460/9560 Jefferson Peak (JfP)". Other users with other Intel adapters
such as the AX211 do not have the same problem. I also attached a CSR
USB-to-Bluetooth adapter to the affected system, and the mouse works
fine, even on the bad kernel versions 6.11-rc1 and up.
I did diagnostic testing using git bisect and building the LINUX
kernel from source on the affected machine. The sequence I found is
here:
git bisect start
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
git bisect bad 280e36f0d5b997173d014c07484c03a7f7750668
git bisect good 0434dbe32053d07d658165be681505120c6b1abc
git bisect good 80ab5445da623540ea6303740015dd0210a06dc8
git bisect bad e2f710f97f3544df08ebe608c8157536e0ffb494
git bisect bad 586f14a6a182bbdb9404dc66464dcd8d0ac175a3
git bisect bad f6dc9214e526c2f735d93b5330f4dcd42a2b5308
git bisect good 464b99e77b3d024a319db0dabe917d04824039db
git bisect good b1c7cd6caaf6209ed9f7df59b61a2ac885eb79b3
git bisect bad fb5e4713fc185f6283ba0704edccea312253e805
git bisect bad 27489364299a2ddb5c54cd9f29a3f41bd8d151ab
git bisect good d4cc4ee48167b4c25abf49ead19412c29a1ad9f4
git bisect bad 08c22b52262041164990eef4b0e076bce173a3b2
git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
The final result is that this commit is the one that breaks the mouse
for the Intel 9460/9560 adapter:
$ git bisect bad f25b7fd36cc3a850e006aed686f5bbecd200de1b
f25b7fd36cc3a850e006aed686f5bbecd200de1b is the first bad commit
commit f25b7fd36cc3a850e006aed686f5bbecd200de1b
Author: Ying Hsu <yinghsu@chromium.org>
Date: Wed May 29 08:00:00 2024 +0000
Bluetooth: Add vendor-specific packet classification for ISO data
When HCI raw sockets are opened, the Bluetooth kernel module doesn't
track CIS/BIS connections. User-space applications have to identify
ISO data by maintaining connection information and look up the mapping
for each ACL data packet received. Besides, btsnoop log captured in
kernel couldn't tell ISO data from ACL data in this case.
To avoid additional lookups, this patch introduces vendor-specific
packet classification for Intel BT controllers to distinguish
ISO data packets from ACL data packets.
Signed-off-by: Ying Hsu <yinghsu@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
drivers/bluetooth/btintel.c | 25 +++++++++++++++++++++++--
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 16 ++++++++++++++++
3 files changed, 40 insertions(+), 2 deletions(-)
I am pretty sure this commit affects one file in the modules package,
but it might be in another package from the same kernel update. The
whole update from the apt.log is here:
Start-Date: 2025-02-12 12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12 12:55:35
Start-Date: 2025-02-12 15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12 15:26:12
Currently, I can boot from kernel 6.10.14 and get my mouse working
again, so this is not a show-stopper bug.
I'm willing to help test/diagnose further, if needed.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
Uname: Linux 6.11.0-17-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 14:33:40 2025
Dependencies:
InstallationDate: Installed on 2024-04-29 (304 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: linux-hwe-6.11
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: dchang 3365 F.... pipewire
/dev/snd/controlC0: dchang 3370 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-29 (309 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Star Labs StarLite
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=40a0d991-e225-4f4b-8cb9-dee8d07c661a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.11.0-17-generic N/A
linux-backports-modules-6.11.0-17-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
Tags: noble
Uname: Linux 6.11.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/28/2025
dmi.bios.release: 24.8
dmi.bios.vendor: coreboot
dmi.bios.version: 25.01
dmi.board.name: StarLite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 32
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 25.1
dmi.modalias: dmi:bvncoreboot:bvr25.01:bd01/28/2025:br24.8:efr25.1:svnStarLabs:pnStarLite:pvr1.0:rvnStarLabs:rnStarLite:rvr1.0:cvnStarLabs:ct32:cvr1.0:skuI5:
dmi.product.family: I5
dmi.product.name: StarLite
dmi.product.sku: I5
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions
Комментариев нет:
Отправить комментарий