Kernel >=5.9 breaks bluetooth mouse connection

alexxedo · 2020-10-18 10:29:54

Hi everyone !

I just update my kernel to 5.9.1 and my Logitech Anywhere MX 2 mouse does not reconnect after a reboot.
I have to re-pair it at each boot to get it working. Trying to reconnect it returns a connection abort in blueman-applet.
I was unable to get any more detailed logs in journalct/dmesg/bluetoothctl

Got the same behavior with 5.9.0 Downgrading to 5.8.14 solves the issue.

Bluetooth card is a Intel AX200 card.

Anyone's getting this ?

Last edited by alexxedo (2020-10-18 10:30:17)

baalholm · 2020-10-18 12:44:10

Yes, it's exactly the same for me, in my case the mouse is Logitech MX Vertical and bluetooth controller is Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP). On the other hand, already paired bluetooth headsets do reconnect and work after reboot (I have tried with Sony WI-1000XM2 and Bose QuietControl 30).

hexchain · 2020-10-18 12:54:44

Same for me too with AX200 + Anywhere MX 2S. The mouse is a BLE device I believe.

I also have a Sony MDR-1000X Bluetooth headset (not BLE) which works perfectly fine. I suspect the problem happens with BLE only.

LnJimMoen · 2020-10-18 13:36:01

Intel AC 9560.
Both the mobile phone and the Bluetooth headset can be connected normally. However, a Bluetooth mouse that only supports BLE cannot automatically connect.

Look the file /var/lib/xxx/yyy/info
Phone/headset:
...
SupportedTechnologies=BR/EDR;LE;
...

Mouse:
...
SupportedTechnologies=LE;
...

mskmsk · 2020-10-18 15:18:41

Same for my Logitech MX Master 2S + AX200 and I have to downgrade to kernel 5.8 to solve the issue.

romstor · 2020-10-18 16:43:31

The same here with Bose QC35 headset. Was working great for a long time over bluetooth. Noticed yesterday after upgrade to kernel 5.9.1 - headset didn't reconnect to its profile. I had to delete the profile and pair it again. It then connected and worked ok. This morning - trying to re-connect - it kept saying it is "connecting". I could see some traffic shown in Blueman, but connection didn't succeed. I again needed to remove the device and pair it again - and then it worked.

I checked and all the drivers seem to be loading fine:

$ lsusb | grep -i bluetooth
Bus 001 Device 003: ID 0bda:8723 Realtek Semiconductor Corp. RTL8723A Bluetooth

$ lsmod | grep -i bt
btcoexist             217088  1 rtl8723ae
rtlwifi               131072  4 rtl_pci,btcoexist,rtl8723ae,rtl8723_common
btusb                  69632  0
btrtl                  24576  1 btusb
btbcm                  20480  1 btusb
btintel                32768  1 btusb
bluetooth             741376  44 btrtl,btintel,btbcm,bnep,btusb,rfcomm
btrfs                1523712  1
libcrc32c              16384  1 btrfs
xor                    24576  1 btrfs
raid6_pq              122880  1 btrfs

Noticed interesting errors in dmesg that I don't see were there before:

$ dmesg | grep -i bluetooth
[    3.261722] usb 1-1.3: Product: RT Bluetooth Radio
[    4.915893] Bluetooth: Core ver 2.22
[    4.915922] Bluetooth: HCI device and connection manager initialized
[    4.915928] Bluetooth: HCI socket layer initialized
[    4.915931] Bluetooth: L2CAP socket layer initialized
[    4.915940] Bluetooth: SCO socket layer initialized
[    5.347082] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
[    5.347087] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723a_fw.bin
[    6.020073] Bluetooth: hci0: RTL: fw version 0x0e3da5b1
[    6.618552] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.618555] Bluetooth: BNEP filters: protocol multicast
[    6.618562] Bluetooth: BNEP socket layer initialized
[   11.702770] Bluetooth: RFCOMM TTY layer initialized
[   11.702779] Bluetooth: RFCOMM socket layer initialized
[   11.702790] Bluetooth: RFCOMM ver 1.11
[   78.433794] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[ 6714.557333] Bluetooth: hci0: link tx timeout
[ 6714.557351] Bluetooth: hci0: killing stalled connection 04:52:c7:08:48:95

~~That "killing stalled connection".... hmmm - never happened before.~~ EDIT: That was me walking out of range - it is ok.

But this "Ignoring error of Inquiry Cancel command" on second 78 after boot - this is when I turned my headset on i think and it didn't connect...

Looks like something got screwed up in the kernel and it doesn't seem to be specific hardware or driver - something in the kernel that manages BT.

EDIT 2: Some parse errors from bluetoothd in journalctl - that can't be right:

$ journalctl -b | grep -i bluetooth
Oct 18 09:39:49 ipc kernel: usb 1-1.3: Product: RT Bluetooth Radio
Oct 18 09:39:50 ipc kernel: Bluetooth: Core ver 2.22
Oct 18 09:39:50 ipc kernel: Bluetooth: HCI device and connection manager initialized
Oct 18 09:39:50 ipc kernel: Bluetooth: HCI socket layer initialized
Oct 18 09:39:50 ipc kernel: Bluetooth: L2CAP socket layer initialized
Oct 18 09:39:50 ipc kernel: Bluetooth: SCO socket layer initialized
Oct 18 09:39:50 ipc kernel: Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=1200
Oct 18 09:39:50 ipc kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723a_fw.bin
Oct 18 09:39:51 ipc kernel: Bluetooth: hci0: RTL: fw version 0x0e3da5b1
Oct 18 09:39:51 ipc systemd[1]: Starting Bluetooth service...
Oct 18 09:39:52 ipc bluetoothd[340]: Bluetooth daemon 5.55
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanType” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanWindow” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanType” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanWindow” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRLinkSupervisionTimeout” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRPageTimeout” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRMinSniffInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “BRMaxSniffInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEMinAdvertisementInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEMaxAdvertisementInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEMultiAdvertisementRotationInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAutoConnect” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAutoConnect” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalSuspend” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowSuspend” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalDiscovery” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowDiscovery” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAdvMonitor” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAdvMonitor” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Oct 18 09:39:52 ipc bluetoothd[340]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Oct 18 09:39:52 ipc systemd[1]: Started Bluetooth service.
Oct 18 09:39:52 ipc systemd[1]: Reached target Bluetooth.
Oct 18 09:39:52 ipc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 18 09:39:52 ipc bluetoothd[340]: Starting SDP server
Oct 18 09:39:52 ipc kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 18 09:39:52 ipc kernel: Bluetooth: BNEP filters: protocol multicast
Oct 18 09:39:52 ipc kernel: Bluetooth: BNEP socket layer initialized
Oct 18 09:39:52 ipc bluetoothd[340]: Bluetooth management interface 1.18 initialized
Oct 18 09:39:52 ipc dbus-daemon[341]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=340 comm="/usr/lib/bluetooth/bluetoothd ")
Oct 18 09:39:57 ipc bluetoothd[340]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/sbc
Oct 18 09:39:57 ipc bluetoothd[340]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/sbc
Oct 18 09:39:57 ipc kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 18 09:39:57 ipc kernel: Bluetooth: RFCOMM socket layer initialized
Oct 18 09:39:57 ipc kernel: Bluetooth: RFCOMM ver 1.11
Oct 18 09:39:59 ipc systemd[1]: Starting Bluetooth management mechanism...
Oct 18 09:40:00 ipc systemd[1]: Started Bluetooth management mechanism.
Oct 18 09:40:00 ipc systemd[483]: Starting Bluetooth OBEX service...
Oct 18 09:40:00 ipc systemd[483]: Started Bluetooth OBEX service.
Oct 18 09:41:01 ipc kernel: Bluetooth: hci0: Ignoring error of Inquiry Cancel command
Oct 18 09:41:11 ipc systemd[483]: Reached target Bluetooth.
Oct 18 09:41:20 ipc bluetoothd[340]: /org/bluez/hci0/dev_04_52_C7_08_48_95/sep1/fd0: fd(45) ready
Oct 18 11:31:37 ipc kernel: Bluetooth: hci0: link tx timeout
Oct 18 11:31:37 ipc kernel: Bluetooth: hci0: killing stalled connection 04:52:c7:08:48:95
Oct 18 11:31:37 ipc bluetoothd[340]: profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
Oct 18 11:31:37 ipc dbus-daemon[341]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.31" (uid=1000 pid=578 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.4" (uid=0 pid=340 comm="/usr/lib/bluetooth/bluetoothd ")
Oct 18 11:31:37 ipc bluetoothd[340]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 18 11:31:37 ipc bluetoothd[340]: src/profile.c:ext_io_disconnected() Unable to get io data for Phone Book Access: getpeername: Transport endpoint is not connected (107)

EDIT 3: Looks like in most cases, when I turn on a bluetooth device and as it starts connecting - restarting bluetooth.service gets the devices connected again:

sudo systemctl restart bluetooth

With my headphones though it is always asking to accept the device - so it looks like it is kind of "stuck" in the pairing mode or something...

Last edited by romstor (2020-10-18 18:52:25)

alexxedo · 2020-10-18 18:35:04

Yes I think something has been modified in the kernel resulting in this behaviour.
If I remember well there was some Bluetooth related corrections made recently about security issues.

hexchain · 2020-10-18 20:07:39

It already happens in kernel 5.9.0, which is before the security fix (5.9.1).

pilililo2 · 2020-10-18 23:30:11

Yup, having exactly the same problem on 5.9.1 with the MX Anywhere 2S. Downgrading to 5.8 kernel series fixes the issue.

alexxedo · 2020-10-19 06:14:56

@all people having the anywhere mx 2. Even on 5.8 I noticed that the mouse reconnects after session is opened but then freezes for 2 seconds and next reworks ok.
Already tried a lot of thing especially tweaking power management (usb autosuspend) but nothing really fixed the problem.

Has anyone fixed this ?

Last edited by alexxedo (2020-10-19 06:19:11)

mskmsk · 2020-10-19 06:59:58

Not yet. Similar symptom occurs when testing under Debian & Fedora.

alexxedo wrote:

@all people having the anywhere mx 2. Even on 5.8 I noticed that the mouse reconnects after session is opened but then freezes for 2 seconds and next reworks ok.
Already tried a lot of thing especially tweaking power management (usb autosuspend) but nothing really fixed the problem.
Has anyone fixed this ?

denomolo · 2020-10-19 08:53:42

Same here. Need to unpair and pair again after boot or sleep. It's a pain

duama · 2020-10-19 10:06:02

Same with Intel AX200 and Logitech M590.

A temporary solution is to disable Link Layer Privacy.

My patch:

diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
index 9873e1c8cd16..7ed862135110 100644
--- a/include/net/bluetooth/hci_core.h
+++ b/include/net/bluetooth/hci_core.h
@@ -1363,7 +1363,7 @@ void hci_conn_del_sysfs(struct hci_conn *conn);
                         ((dev)->le_rx_def_phys & HCI_LE_SET_PHY_CODED))
 
 /* Use LL Privacy based address resolution if supported */
-#define use_ll_privacy(dev) ((dev)->le_features[0] & HCI_LE_LL_PRIVACY)
+#define use_ll_privacy(dev) (0)
 
 /* Use ext scanning if set ext scan param and ext scan enable is supported */
 #define use_ext_scan(dev) (((dev)->commands[37] & 0x20) && \

With the above patch, my bluetooth mouse is able to reconnect again.

mcloaked · 2020-10-19 10:36:45

Has anyone reported upstream to kernel bugzilla on this issue?

There are already other upstream reports of issues with bluetooth for kernel >5.9 such as https://bugzilla.kernel.org/show_bug.cgi?id=209717 and https://bugzilla.kernel.org/show_bug.cgi?id=209403

Last edited by mcloaked (2020-10-19 10:40:21)

mskmsk · 2020-10-19 12:04:15

yup, I just reported https://bugzilla.kernel.org/show_bug.cgi?id=209745

mcloaked wrote:

Has anyone reported upstream to kernel bugzilla on this issue?
There are already other upstream reports of issues with bluetooth for kernel >5.9 such as https://bugzilla.kernel.org/show_bug.cgi?id=209717 and https://bugzilla.kernel.org/show_bug.cgi?id=209403

Alkotronikk · 2020-10-19 14:31:35

Confirming that MX3 is affected too.

loqs · 2020-10-19 14:36:00

What if you apply https://github.com/torvalds/linux/commi … 4080d6e766
Edit
If the above fails what if you revert https://github.com/torvalds/linux/commi … eb55a22beb does that work?

Last edited by loqs (2020-10-19 14:38:42)

duama · 2020-10-19 16:34:49

loqs wrote:

What if you apply https://github.com/torvalds/linux/commi … 4080d6e766
Edit
If the above fails what if you revert https://github.com/torvalds/linux/commi … eb55a22beb does that work?

Applying c0ee0644df5da3f877a53e402d03634080d6e766 doesn't help.

Reverting e1d572357599d142df5764b39731b6eb55a22beb causes conflicts and I'm not sure how to resolve them.

hexchain · 2020-10-19 21:54:53

Can confirm #13 also works for me.

EDIT: And c0ee0644df5da3f877a53e402d03634080d6e766 doesn't help either.

Last edited by hexchain (2020-10-19 22:34:21)

loqs · 2020-10-20 00:18:01

I could not get e1d572357599d142df5764b39731b6eb55a22beb to revert cleanly either, gave up after 4 additional reverts was not enough.
What if you its checkout parent 6540351e6f27ef718e3cf5b46349633f3ec57859 or bisect between 5.8 and 5.9?

mskmsk · 2020-10-20 00:33:04

Downgraded and waiting for a fix.

Last edited by mskmsk (2020-10-20 00:40:19)

Brocellous · 2020-10-20 01:52:27

romstor wrote:

The same here with Bose QC35 headset.

No issues here with my QC35 on kernel 5.9.1. I think you have an unrelated issue.

leshyleshy · 2020-10-21 03:58:13

Hey guys, I am on 5.4.72-1-lts I also experiencing something similar thought it was just me. Basically my newer bose 700 headset wont pair or connect properly. I am also seeing this "Key file" message in the systemd status. I initially thought my problem might be related to group permissions with the LP group so i followed these instructions and edited some configs https://gist.github.com/yejun/2c1a070a8 … 8a998b5495 Weirdly enough the headphones paired briefly but then the sound quality was muddy and then it just got disconnected immediately. I actually dont know what i did but for one reason or another the bluetooth randomly pairs then disconnects. The weird part was that the headphones paired the first time I tried as well, and also the first time I tried connecting as root with bluetoothctl. Its like it trusts new devices then untrusts them, at least thats what I observed. PS. someone smart please lemme know if I should change my settings back I think i may have I think i may have overdone it trying to fix this.

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2020-10-21 11:12:15 PST; 9min ago
       Docs: man:bluetoothd(8)
   Main PID: 632 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 19134)
     Memory: 3.5M
     CGroup: /system.slice/bluetooth.service
             └─632 /usr/lib/bluetooth/bluetoothd

Oct 21 11:12:15 archPC bluetoothd[632]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Oct 21 11:12:15 archPC bluetoothd[632]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Oct 21 11:12:15 archPC bluetoothd[632]: Starting SDP server
Oct 21 11:12:15 archPC bluetoothd[632]: Bluetooth management interface 1.14 initialized
Oct 21 11:12:16 archPC bluetoothd[632]: Endpoint registered: sender=:1.3 path=/MediaEndpoint/A2DPSink/sbc
Oct 21 11:12:16 archPC bluetoothd[632]: Endpoint registered: sender=:1.3 path=/MediaEndpoint/A2DPSource/sbc
Oct 21 11:18:48 archPC bluetoothd[632]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/sbc
Oct 21 11:18:48 archPC bluetoothd[632]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/sbc
Oct 21 11:18:48 archPC bluetoothd[632]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Oct 21 11:18:48 archPC bluetoothd[632]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)

I tried connecting from bluetoothctl while I checked out btmon and I see this "Host is down error" when I try and connect.

Bluetoothctl console

[bluetooth]# connect 4C:87:5D:A0:BC:45
Attempting to connect to 4C:87:5D:A0:BC:45
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
Failed to connect: org.bluez.Error.Failed

BTMON

< HCI Command: Create Connection (0x01|0x0005) plen 13                                                                                               #7 [hci0] 88.133593
        Address: XX:XX:XX:XX:XX:XX (Bose Corporation)
        Packet type: 0xcc18
          DM1 may be used
          DH1 may be used
          DM3 may be used
          DH3 may be used
          DM5 may be used
          DH5 may be used
        Page scan repetition mode: R2 (0x02)
        Page scan mode: Mandatory (0x00)
        Clock offset: 0x0000
        Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4                                                                                                            #8 [hci0] 88.286587
      Create Connection (0x01|0x0005) ncmd 1
        Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11                                                                                                         #9 [hci0] 93.492383
        Status: Page Timeout (0x04)
        Handle: 65535
        Address: 4C:87:5D:A0:BC:45 (Bose Corporation)
        Link type: ACL (0x01)
        Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8                                                                                                   {0x0001} [hci0] 93.492413
        BR/EDR Address: XX:XX:XX:XX:XX:XX (Bose Corporation)
        Status: Connect Failed (0x04)
= bluetoothd: src/profile.c:record_cb() Unable to get Headset Voice gateway SDP record: Host is down                                                           93.492932

Last edited by leshyleshy (2020-10-21 03:59:46)

hexchain · 2020-10-21 08:19:53

I think your problem is the same as #6, hence also unrelated to this thread.

leshyleshy wrote:

Hey guys, I am on 5.4.72-1-lts I also experiencing something similar thought it was just me. Basically my newer bose 700 headset wont pair or connect properly. I am also seeing this "Key file" message in the systemd status.

ASRMarco13 · 2020-10-23 11:21:59

Same for my Logitech MX Ergo + AX200 with kernel 5.9.1.

Arch Linux

#1 2020-10-18 10:29:54

Kernel >=5.9 breaks bluetooth mouse connection

#2 2020-10-18 12:44:10

Re: Kernel >=5.9 breaks bluetooth mouse connection

#3 2020-10-18 12:54:44

Re: Kernel >=5.9 breaks bluetooth mouse connection

#4 2020-10-18 13:36:01

Re: Kernel >=5.9 breaks bluetooth mouse connection

#5 2020-10-18 15:18:41

Re: Kernel >=5.9 breaks bluetooth mouse connection

#6 2020-10-18 16:43:31

Re: Kernel >=5.9 breaks bluetooth mouse connection

#7 2020-10-18 18:35:04

Re: Kernel >=5.9 breaks bluetooth mouse connection

#8 2020-10-18 20:07:39

Re: Kernel >=5.9 breaks bluetooth mouse connection

#9 2020-10-18 23:30:11

Re: Kernel >=5.9 breaks bluetooth mouse connection

#10 2020-10-19 06:14:56

Re: Kernel >=5.9 breaks bluetooth mouse connection

#11 2020-10-19 06:59:58

Re: Kernel >=5.9 breaks bluetooth mouse connection

#12 2020-10-19 08:53:42

Re: Kernel >=5.9 breaks bluetooth mouse connection

#13 2020-10-19 10:06:02

Re: Kernel >=5.9 breaks bluetooth mouse connection

#14 2020-10-19 10:36:45

Re: Kernel >=5.9 breaks bluetooth mouse connection

#15 2020-10-19 12:04:15

Re: Kernel >=5.9 breaks bluetooth mouse connection

#16 2020-10-19 14:31:35

Re: Kernel >=5.9 breaks bluetooth mouse connection

#17 2020-10-19 14:36:00

Re: Kernel >=5.9 breaks bluetooth mouse connection

#18 2020-10-19 16:34:49

Re: Kernel >=5.9 breaks bluetooth mouse connection

#19 2020-10-19 21:54:53

Re: Kernel >=5.9 breaks bluetooth mouse connection

#20 2020-10-20 00:18:01

Re: Kernel >=5.9 breaks bluetooth mouse connection

#21 2020-10-20 00:33:04

Re: Kernel >=5.9 breaks bluetooth mouse connection

#22 2020-10-20 01:52:27

Re: Kernel >=5.9 breaks bluetooth mouse connection

#23 2020-10-21 03:58:13

Re: Kernel >=5.9 breaks bluetooth mouse connection

#24 2020-10-21 08:19:53

Re: Kernel >=5.9 breaks bluetooth mouse connection

#25 2020-10-23 11:21:59

Re: Kernel >=5.9 breaks bluetooth mouse connection

Board footer