The bug is still here in 5.12.13 with asaus m-rbb93 logitech b370 mouse. After some time (unpredictable, can be few hours or few minutes) mouse pointer stops responding, though mouse appears conneceted in the bluetoothctl.
> bluetoothctl
Agent registered
[Bluetooth Travel Mouse]# info
Device 00:07:61:68:D2:9E (public)
Name: Bluetooth Travel Mouse
Alias: Bluetooth Travel Mouse
Class: 0x00002580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes WakeAllowed: yes LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v046DpB002d4809
journalctl and dmesg is silent when the mouse stops responding. Is there any other way to debug this?
When mouse is first connected, dmesg has the message mentioned as the topic of this bug:
[185307.429898] hid-generic 0005:046D:B002.002C: input,hidraw1: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on dc:e9:94:7e:5f:86
[187430.340610] hid-generic 0005:046D:B002.002D: unknown main item tag 0x0
[187430.340668] input: Bluetooth Travel Mouse as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:1/0005:046D:B002.002D/input/input104
The bug is still here in 5.12.13 with asaus m-rbb93 logitech b370 mouse. After some time (unpredictable, can be few hours or few minutes) mouse pointer stops responding, though mouse appears conneceted in the bluetoothctl.
> bluetoothctl
WakeAllowed: yes
LegacyPairing: no 0000-1000- 8000-00805f9b34 fb) 0000-1000- 8000-00805f9b34 fb)
Agent registered
[Bluetooth Travel Mouse]# info
Device 00:07:61:68:D2:9E (public)
Name: Bluetooth Travel Mouse
Alias: Bluetooth Travel Mouse
Class: 0x00002580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
UUID: Human Interface Device... (00001124-
UUID: PnP Information (00001200-
Modalias: usb:v046DpB002d4809
journalctl and dmesg is silent when the mouse stops responding. Is there any other way to debug this?
When mouse is first connected, dmesg has the message mentioned as the topic of this bug: B002.002C: input,hidraw1: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on dc:e9:94:7e:5f:86 B002.002D: unknown main item tag 0x0 pci0000: 00/0000: 00:08.1/ 0000:05: 00.4/usb3/ 3-3/3-3: 1.0/bluetooth/ hci0/hci0: 1/0005: 046D:B002. 002D/input/ input104
[185307.429898] hid-generic 0005:046D:
[187430.340610] hid-generic 0005:046D:
[187430.340668] input: Bluetooth Travel Mouse as /devices/
(In reply to jbMacAZ from comment #5) /git.kernel. org/pub/ scm/linux/ kernel/ git/stable/ linux-stable- rc.git/ ?id=c4c285da1ee 18582ace366f07e 56e355c20ebc49 which is in kernel 4.15.
> The issue was fixed for the Asus T100 (baytrail) 2-in-1 family. See this
> commit.
> https:/
> commit/
Is there a way to enable this system-wide without patching a kernel, for a quick test?
I tried to add btusb.enable_ autosuspend= n kernel paremeter:
# cat /proc/cmdline /boot/vmlinuz- 5.12.13- 1-default root=UUID= ece1a448- 6944-4f34- a61c-1742fde2ac 3c splash=silent psi=1 nvidia- drm.modeset= 1 btusb.enable_ autosuspend= n quiet mitigations=auto
BOOT_IMAGE=
# systool -v -m btusb
Module = "btusb"
Attributes: 80496F74C"
coresize = "69632"
initsize = "0"
initstate = "live"
refcnt = "0"
srcversion = "8EADE2557C1471
taint = ""
uevent = <store method only>
version = "0.8"
Parameters: autosuspend = "N"
disable_scofix = "N"
enable_
force_scofix = "N"
reset = "Y"
But this does not resolve the bug