Bluetooth mouse laggy and erratic

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

I noticed the following two lines.

[ 9442.157844] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will not be loaded
[ 9442.157846] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-216f.hcd not found

Did you try the firmware as https://wiki.archlinux.org/index.php/Dell_XPS_13_%282015%29#Bluetooth mentioned.

http://askubuntu.com/questions/613614/bluetooth-not-working-in-ubuntu-15-04 also mentioned this firmware.

https://askubuntu.com/questions/617513/bluetooth-not-connecting-to-devices-even-though-it-recognizes-them also.

I followed the instructions available here:

http://askubuntu.com/questions/613614/bluetooth-not-working-in-ubuntu-15-04

That is, I did:

wget https://www.dropbox.com/s/r2pb41rhx65t9zi/BCM20702A0-0a5c-216f.hcd
sudo cp BCM20702A0-0a5c-216f.hcd /lib/firmware/brcm/
sudo modprobe -r btusb
sudo modprobe btusb

@cribari: What is the result?

@fourdollars I did that when I first installed Ubuntu 15.04 on my new DELL XPS 13 (2015 edition, model 9343, bios A03). I was then able to pair devices via bluetooth. Nonetheless, I faced two major problems after that: 1) my bluetooth mouse became laggy and erratic after a suspend (to RAM) and resume (both DELL and Microsoft mice). 2) frequent freezes/crashes when I tried to suspend (blank screen, CAPS LOCK key blinking, unable to ssh into the machine). Last night I did a fresh reinstall of Ubuntu 15.04.

The problem just happened to me again. I am including bellow the dmesg information.

[39935.550219] ACPI: Waking up from system sleep state S3
[39936.749233] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[39936.749486] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[39936.749535] PM: noirq resume of devices complete after 16.818 msecs
[39936.772659] PM: early resume of devices complete after 23.055 msecs
[39936.772771] usb usb1: root hub lost power or was reset
[39936.772772] usb usb2: root hub lost power or was reset
[39936.773878] sd 3:0:0:0: [sda] Starting disk
[39936.774743] rtc_cmos 00:01: System wakeup disabled by ACPI
[39936.957171] cfg80211: Calling CRDA to update world regulatory domain
[39937.000773] usb 3-1: reset high-speed USB device number 2 using ehci-pci
[39937.096852] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[39937.098948] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[39937.099202] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[39937.099240] ata4.00: configured for UDMA/133
[39937.277116] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[39937.406403] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e00
[39937.406404] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e90
[39937.406405] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e48
[39937.406412] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979948
[39937.406413] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979900
[39937.406413] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979288
[39937.406414] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979240
[39937.517280] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[39937.645962] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d90cd3c0
[39937.645963] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d90cd408
[39937.645976] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[39937.757453] usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[39937.995391] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d8fb2f60
[39937.995398] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d8fb2f00
[39938.038325] PM: resume of devices complete after 1264.639 msecs
[39938.038849] ------------[ cut here ]------------
[39938.038853] WARNING: CPU: 1 PID: 8500 at /build/buildd/linux-3.19.0/drivers/base/firmware_class.c:1126 _request_firmware+0x72e/0xbd0()
[39938.038877] Modules linked in: cpuid mmc_block ses enclosure uas usb_storage hid_generic hidp binfmt_misc rfcomm bnep nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_core bluetooth v4l2_common videodev usbhid media dell_led joydev dell_wmi hid_multitouch sparse_keymap dell_laptop dcdbas intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_realtek i915_bpo intel_powerclamp coretemp wl(POE) snd_hda_codec_...

I then did

sudo modprobe -r btusb
sudo modprobe btusb

and the BT mouse was no longer laggy and erratic.

The problem just happened again. I am enclosing below information obtained from dmesg.

[54069.332038] CPU3 is up
[54069.335595] ACPI: Waking up from system sleep state S3
[54070.521751] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[54070.522779] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[54070.522842] PM: noirq resume of devices complete after 17.080 msecs
[54070.545697] PM: early resume of devices complete after 22.808 msecs
[54070.545796] usb usb1: root hub lost power or was reset
[54070.545798] usb usb2: root hub lost power or was reset
[54070.547460] rtc_cmos 00:01: System wakeup disabled by ACPI
[54070.561611] sd 3:0:0:0: [sda] Starting disk
[54070.730554] cfg80211: Calling CRDA to update world regulatory domain
[54070.781847] usb 3-1: reset high-speed USB device number 2 using ehci-pci
[54070.881907] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[54070.884034] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[54070.884415] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[54070.884447] ata4.00: configured for UDMA/133
[54071.050074] usb 1-5: reset high-speed USB device number 4 using xhci_hcd
[54071.288028] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d8fb2f60
[54071.288029] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d8fb2f00
[54071.402440] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[54071.531804] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e00
[54071.531806] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e90
[54071.531806] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802149b9e48
[54071.531807] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979948
[54071.531808] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979900
[54071.531808] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979288
[54071.531809] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880212979240
[54071.642640] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[54071.771282] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d90cd3c0
[54071.771283] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800d90cd408
[54071.771291] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[54071.776773] PM: resume of devices complete after 1230.077 msecs
[54071.777403] PM: Finishing wakeup.
[54071.777404] Restarting tasks ...
[54071.777731] pci_bus 0000:01: Allocating resources
[54071.777846] pci_bus 0000:02: Allocating resources
[54071.777890] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[54071.779421] pci_bus 0000:01: Allocating resources
[54071.779540] pci_bus 0000:02: Allocating resources
[54071.779584] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[54071.779658] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[54071.779754] i915 0000:00:02.0: BAR 6: [??? 0x...

Status changed to 'Confirmed' because the bug affects multiple users.

I observe this in a 15.10 installation.

Linux 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 23:32:28 UTC 2015 i686 i686 i686 GNU/Linux

I'm using a logitech bluetooth kb+mouse. Everything works normally, then I watch a movie in Kodi and when I exit to desktop again, mouse is very laggy. So some kind of usb suspend might be involved.

Within Kodi, after a while, the keyboard won't even reconnect so I have to exit with a remote. Once in the desktop the slugginesh manifests itself.

Reloading the module as in comment #10 works for me, thanks for the workaround.

I am seeing this with a Logitech Bluetooth Laser travel Mouse on Ubuntu-16.04.
(The system is set to not sleep or suspend.)

The fix mentioned above seems to work:

  sudo modprobe -r btusb
  sudo modprobe btusb

Here is some output from dmesg:

[ 11.035464] vboxdrv: Found 8 processor cores
[ 11.053922] vboxdrv: TSC mode is Invariant, tentative frequency 2712000012 Hz
[ 11.053924] vboxdrv: Successfully loaded version 5.0.16_Ubuntu (interface 0x00240000)
[ 11.058160] VBoxNetFlt: Successfully started.
[ 11.061432] VBoxNetAdp: Successfully started.
[ 11.064505] VBoxPciLinuxInit
[ 11.067342] vboxpci: IOMMU not found (not registered)
[ 12.027559] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 12.027562] Bluetooth: HIDP socket layer initialized
[ 12.028358] hid-generic 0005:046D:B008.0002: unknown main item tag 0x0
[ 12.028479] input: Bluetooth Laser Travel Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:046D:B008.0002/input/input13
[ 12.029348] hid-generic 0005:046D:B008.0002: input,hidraw1: BLUETOOTH HID v3.14 Mouse [Bluetooth Laser Travel Mouse] on a4:34:d9:93:30:9f
[ 124.165037] hid-generic 0005:046D:B318.0003: unknown main item tag 0x0
[ 124.165164] input: Logitech K760 as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:512/0005:046D:B318.0003/input/input14
[ 124.165511] hid-generic 0005:046D:B318.0003: input,hidraw2: BLUETOOTH HID v1.1b Keyboard [Logitech K760] on a4:34:d9:93:30:9f
[ 149.711166] hid-generic 0005:046D:B318.0004: unknown main item tag 0x0
[ 149.711466] input: Logitech K760 as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:512/0005:046D:B318.0004/input/input15
[ 149.712161] hid-generic 0005:046D:B318.0004: input,hidraw2: BLUETOOTH HID v1.1b Keyboard [Logitech K760] on a4:34:d9:93:30:9f
[ 168.931084] logitech-hidpp-device 0005:046D:B00C.0005: unknown main item tag 0x0
[ 168.943063] logitech-hidpp-device 0005:046D:B00C.0005: HID++ 2.0 device connected.
[ 169.059414] input: Logitech Rechargeable Trackpad T651 as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:768/0005:046D:B00C.0005/input/input16
[ 169.059652] logitech-hidpp-device 0005:046D:B00C.0005: input,hidraw3: BLUETOOTH HID v5.00 Mouse [Logitech Rechargeable Trackpad T651] on a4:34:d9:93:30:9f

I have Samsung bluetooth keyboard bkb10 and laptop with bcm 43142 bluetooth adapter. Keyboard is very laggy(unsusable), and also connection drops frequetly (i guess usually it is kernel bug causing drops, it drops every time after some intel i915 bug in kernel, but not always after that intel bug). So i tried to install older bluez from bluez.org, and it works great now! It is stable on 5.27 Bluez, but starting from 5.28 keyboard is unusable. Try it, maybe it will help you also.

I have to add that keyboard is not laggy with old bluez, but it is still disconnecting frequently.

Bluez 5.40 on Ubuntu and 5.38 on CM12.1 phone also laggy. But one detail could help devs to find the bug. While pairing keyboard with PC i see a number, that i have to type on the keyboard to connect it it. So typing that numbers is always very fast and stable, i did try it a lot of times. But once paired, it becomes laggy, buggy, unusable.

Hey, thanks for the updates and the investigation. However just to clarify, you are talking about this keyboard http://www.sonymobile.com/global-en/products/accessories/bluetooth-keyboard-bkb10/ right? Also, do I understand rightly that once it is paired the connection gets disconnected?

As an addition to that could you paste the syslog with Bluetooth debug options enabled [you can find instructions there https://wiki.ubuntu.com/DebuggingBluetooth]? This is going to be really useful for us when we start working on this issue.

Thanks

Thank you for your work)
The keyboard is http://www.samsung.com/us/support/owners/product/BKB-10USWEGXAR
Once it is paired it just becomes unstable. Big latency, and also Bbbuuuuugs liiike thisss. That particular bug is making it unusable. Also i was checking it in kacpimon, if acpi sees several key presses also, and it does. While that laggs there are no any errors at all in syslog or dmesg, only after disconnect. And it is not disconnected right after pairing. It is very random, but sometimes before error about disconnect drm:intel_pipe_update_end [i915] bug appears, sometimes not. Also important to mention that with windows 10 it works perfectcly (fast, stable, no disconnects). Every Bluez install i was installing with bluetooth library, but now i will try to work with native 5.37 lib and old and stable bluez to find if it is bluez or lib bug. A bit later i will give you my logs with buggy and with stable bluez. syslog with disconnect after intel error:
Jun 28 14:07:03 leonid-Lenovo-G500 kernel: [ 2630.762724] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=154570 end=154571) time 116 us, min 763, max 767, scanline start 762, end 768
Jun 28 14:08:26 leonid-Lenovo-G500 dbus[676]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jun 28 14:08:26 leonid-Lenovo-G500 systemd[1]: Starting Hostname Service...
Jun 28 14:08:26 leonid-Lenovo-G500 dbus[676]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jun 28 14:08:26 leonid-Lenovo-G500 systemd[1]: Started Hostname Service.
Jun 28 14:08:26 leonid-Lenovo-G500 org.gtk.vfs.Daemon[1159]: ** (process:30582): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Jun 28 14:09:10 leonid-Lenovo-G500 gnome-session[1294]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Jun 28 14:09:15 leonid-Lenovo-G500 org.gnome.zeitgeist.SimpleIndexer[1159]: ** (zeitgeist-fts:2368): WARNING **: Unable to get info on application://nautilus-autostart.desktop
Jun 28 14:09:58 leonid-Lenovo-G500 URfkill[667]: device_changed_cb: ideapad_bluetooth
Jun 28 14:09:58 leonid-Lenovo-G500 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 28 14:09:58 leonid-Lenovo-G500 systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 28 14:09:58 leonid-Lenovo-G500 kernel: [ 2805.143113] usb 1-1.3: USB disconnect, device number 4
Jun 28 14:09:58 leonid-Lenovo-G500 acpid: input device has been disconnected, fd 17
Jun 28 14:09:58 leonid-Lenovo-G500 bluetoothd[880]: (bluetoothd:880): GLib-CRITICAL **: Source ID 144 was not found when attempting to remove it
Jun 28 14:09:58 leonid-Lenovo-G500 URfkill[667]: device_changed_cb: hci0
Jun 28 14:09:58 leonid-Lenovo-G500 bluetoothd[880]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/A2DPSource
Jun 28 14:09:58 leonid-Lenovo-G500 systemd-rfkill[1271]: Failed to open device: No such device
Jun 28 14:09:58 leonid-Lenovo-G500 bluetoothd[880]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/A2DPSink
Jun 28 14:09:58 leonid-Lenovo-G500 URfkill[667]: removing killswi...

Thanks. The keyboard that yo use is a Bluetooth Classic one and we do not have much issues with those. Of course, there are high chances that we have not been performing our tests using the same model that you use but just for you to know that the issues with BT Classic are something unusual.

I will check if we are able to link the Intel error to the performance penalty.

Best

The intel error only causes disconnects, but not all of them are because of intel error. Often it disconnects by itself, without any other errors.
And there are no lags and repeatings on older bluez, just disconnects. Another thing is that keyboard was designed for android mainly? so it should work with linux in theory.

Hey, I have checked with our hardware team and it seems the Intel error that you are experiencing should have nothing to do with Bluetooth performance.

Well, you know better than me for sure) But that same mistake appears really often under several linux distributions right before bluetooth keyboard disconnects. Too often to be a coincidence for me.
So, did i activate bluetooth debug options, was my logs as helpful as they can be?

So, right now i am working with new (native ubuntu, 5.37) libbluetooth and with bluez 5.27 downloaded from bluez.org, and there are no lags at all, only disconnects. So i guess the reason for lags is in bluez itself.

I am having this same problem with Logitech m535 bluetooth mouse running Ubuntu 16.04 on a Dell XPS13 9350. Here is the result of the command issued by the OP. Any ideas?

[ 2.817422] Bluetooth: Core ver 2.21
[ 2.817443] Bluetooth: HCI device and connection manager initialized
[ 2.817446] Bluetooth: HCI socket layer initialized
[ 2.817449] Bluetooth: L2CAP socket layer initialized
[ 2.817455] Bluetooth: SCO socket layer initialized
[ 2.826800] Bluetooth: HCI UART driver ver 2.3
[ 2.826803] Bluetooth: HCI UART protocol H4 registered
[ 2.826805] Bluetooth: HCI UART protocol BCSP registered
[ 2.826806] Bluetooth: HCI UART protocol LL registered
[ 2.826807] Bluetooth: HCI UART protocol ATH3K registered
[ 2.826809] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 2.826843] Bluetooth: HCI UART protocol Intel registered
[ 2.826858] Bluetooth: HCI UART protocol BCM registered
[ 2.826859] Bluetooth: HCI UART protocol QCA registered
[ 2.960951] Bluetooth: hci0: BCM: chip id 110
[ 2.977372] Bluetooth: hci0: BCM4350C5
[ 2.977947] Bluetooth: hci0: BCM (003.006.007) build 0000
[ 2.979162] bluetooth hci0: Direct firmware load for brcm/BCM-0a5c-6412.hcd failed with error -2
[ 2.979168] Bluetooth: hci0: BCM: Patch brcm/BCM-0a5c-6412.hcd not found
[ 4.068669] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.068672] Bluetooth: BNEP filters: protocol multicast
[ 4.068676] Bluetooth: BNEP socket layer initialized
[ 6.370274] Bluetooth: RFCOMM TTY layer initialized
[ 6.370281] Bluetooth: RFCOMM socket layer initialized
[ 6.370285] Bluetooth: RFCOMM ver 1.11
[ 43.979826] Bluetooth: hci0: BCM: chip id 110
[ 43.995724] Bluetooth: hci0: BCM4350C5
[ 43.996692] Bluetooth: hci0: BCM (003.006.007) build 0000
[ 43.996725] bluetooth hci0: Direct firmware load for brcm/BCM-0a5c-6412.hcd failed with error -2
[ 43.996727] Bluetooth: hci0: BCM: Patch brcm/BCM-0a5c-6412.hcd not found
[ 368.022543] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 368.022566] Bluetooth: HIDP socket layer initialized
[ 370.269291] input: Bluetooth Mouse M336/M337/M535 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B014.0002/input/input19
[ 370.270218] hid-generic 0005:046D:B014.0002: input,hidraw1: BLUETOOTH HID v12.00 Mouse [Bluetooth Mouse M336/M337/M535] on 30:52:cb:85:2c:ec
[ 1269.884899] Bluetooth: hci0 urb ffff8802731c2c00 failed to resubmit (2)
[ 1280.112502] Bluetooth: hci0: BCM: chip id 110
[ 1280.128489] Bluetooth: hci0: ChromeLinux_658B
[ 1280.129363] Bluetooth: hci0: BCM (003.006.007) build 0000
[ 1280.129420] bluetooth hci0: Direct firmware load for brcm/BCM-0a5c-6412.hcd failed with error -2
[ 1280.129429] Bluetooth: hci0: BCM: Patch brcm/BCM-0a5c-6412.hcd not found
[ 1284.690426] input: Bluetooth Mouse M336/M337/M535 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B014.0003/input/input20
[ 1284.691111] hid-generic 0005:046D:B014.0003: input,hidraw1: BLUETOOTH HID v12.00 Mouse [Bluetooth Mouse M336/M337/M535] on 30:52:cb:85:2c:ec
[ 4944.970706] input: Bluetooth Mouse M336/M337/M535 as /devices/pci0000:00/000...

I am having the same issue running a bluetooth TECKNET BM306 mouse connecting to the internal bluetooth of an EliteBook 8560W running Ubuntu 16.04.

dmesg:

[54507.549501] hid-generic 0005:0A5C:0001.0008: unknown main item tag 0x0
[54507.549630] input: TECKNET BM306 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:11/0005:0A5C:0001.0008/input/input30
[54507.549771] hid-generic 0005:0A5C:0001.0008: input,hidraw0: BLUETOOTH HID v1.29 Mouse [TECKNET BM306] on 40:2c:f4:cb:04:7d

Any help would be appreciated.

I am having the laggy bluetooth mouse issue with a Logitech MX Anywhere 2 and a Lenovo T450s.

The modprobe suggestion from @cribari has worked for me so far, but I've only done 5 minutes of testing at this point, and only one suspend-resume cycle.

Order of operations:
1) suspend/resume/suspend/resume, etc.
2) turn on bluetooth on notebook (mouse was paired weeks ago) [10:19:31 in log below]
3) turn on mouse and experience lag [10:19:36 in log below]
4) execute these commands "sudo modprobe -rv btusb && sleep 1s && sudo modprobe -v btusb" [10:22:33 in log below]
5) mouse is no longer laggy
6) suspend/resume (once)
7) mouse is still not laggy, and appears to be working fine

Oct 4 10:19:31 tbob kernel: [588896.204026] Bluetooth: hci0: read Intel version: 370810011003110e00
Oct 4 10:19:31 tbob kernel: [588896.205078] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
Oct 4 10:19:31 tbob kernel: [588896.521054] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Oct 4 10:19:31 tbob systemd[1]: Reached target Bluetooth.
Oct 4 10:19:31 tbob bluetoothd[3094]: Failed to obtain handles for "Service Changed" characteristic
Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service
Oct 4 10:19:31 tbob bluetoothd[3094]: Error adding Link Loss service
Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service
Oct 4 10:19:31 tbob bluetoothd[3094]: message repeated 2 times: [ Not enough free handles to register service]
Oct 4 10:19:31 tbob bluetoothd[3094]: Current Time Service could not be registered
Oct 4 10:19:31 tbob bluetoothd[3094]: gatt-time-server: Input/output error (5)
Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service
Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service
Oct 4 10:19:31 tbob bluetoothd[3094]: Sap driver initialization failed.
Oct 4 10:19:31 tbob bluetoothd[3094]: sap-server: Operation not permitted (1)
Oct 4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource
Oct 4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink
Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x000c for device EA:4C:A8:24:2D:95
Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x001b for device EA:4C:A8:24:2D:95
Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x003f for device EA:4C:A8:24:2D:95
Oct 4 10:19:37 tbob bluetoothd[3094]: bt_uhid_send: Invalid argument (22)
Oct 4 10:19:37 tbob kernel: [588902.501689] input: MX Anywhere 2 as /devices/virtual/misc/uhid/0005:046D:B013.007C/input/input95
Oct 4 10:19:37 tbob kernel: [588902.502135] hid-generic 0005:046D:B013.007C: input,hidraw4: BLUETOOTH HID v0.07 Keyboard [MX Anywhere 2] on 10:02:B5:80:73:A1
Oct 4 10:19:37 tbob bluetoothd[3094]: message repeated 12 times: [ bt_uhid_send: Invalid argument (22)]
Oct 4 10:22:33 tbob kernel: [589078.328418] usbcore: deregistering interface driver btusb
Oct 4 10:22:33 tbob systemd[1]: bluetooth.target:...

I experience the same bug on my Thinkpad Yoga 260 with Ubuntu 16.04.2 and 4.11.7 kernel (the issue happened also on older kernels) with my Thinkpad Compact Bluetooth Keyboard with Trackpoint. The dmesg output looks like this:

[ 4952.521400] lenovo 0005:17EF:6048.0017: unknown main item tag 0x0
[ 4952.521703] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0017/input/input40
[ 4952.522622] lenovo 0005:17EF:6048.0017: input,hidraw3: BLUETOOTH HID v3.09 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on a4:34:d9:45:7d:7d

Would be perfect if someone has a solution, it's a very annoying bug.

As far as I know, the lag generally happens using bluetooth scanning (searching). Although scanning should be less disruptive than it is, this seems to be a problem that persists even in current Bluez releases.

You might want to try running 'bluetoothctl' and then typing 'scan off'.

Having the same issue with Logitech m535 and dell xps 13 9350 with broadcom bcm4350 card.

I have the same issue laggy only (no disconnects) with all my bluetooth HID devices, and it is the same on both Ubuntu 17.04 as well fedora core 25.
- Keyboard logitech K810
- Mac keyboard
- Dell BT mouse

The problem did not exist on very old versions of bluez at least with the Mac keyboard.

Restarting bluetooth service seems to fix temporarily.
I've tried also with no success:
- to reduce any possible RF interference (GSM phone, distance etc)
- increase NIce level of bluetooth
- stop upower service

I'vvvvvvvve trrrrrrriiiiieeeeeeeed
also "scan off" with no success
(first line from the BT keyboard)

I've tried also (something reported to other sites)
sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
with no success

I have subscribed Konrad to this bug. He told me he had spent time debugging this issue in the past.

I've tried changing the power management from auto to on of the bluetooth driver but with no success as well.

If you have ideas on what to check, I am willing to test it. I like a lot the form factor of the small BT keyboard, and I would like to find a solution

Update. I replaced my USB bluetooth dongle Bluetooth V4.0 to a very old one V2.0 and since a week now I have no problems with any keyboard or with the mouse.

I have a feeling that this is related to bluetooth and wifi coexistence.

https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi#wi-fibluetooth_coexistence

In essence, bleutooth and wifi operate on similar (the same) frequencies and will interfere. Normally this is handled in the firmware/kernel, but there are problems.

Try this:

https://wiki.debian.org/iwlwifi#Troubleshooting

^I agree with John that this must be related to both Bluetooth and Wifi on at the same time. I don't have an RJ45-USBC dongle to confirm however Im able to see an increase in how often the shuddering occurs when using a 5GHz band wifi vs a 2.4GHz.

I was suggested to update the BIOS by another thread post and that did improve my performance, now the shuddering only begins after some network usage while before the mouse was not usable even when sitting at the desktop.

Reloading the btusb module using modprobe like suggested above also removes the shuddering only to come back after a few moments.

Inserting the supplied BT dongle instead of using the internal radios also eliminates the shuddering but then removes one of the highly valuable USB ports and inevitably will have this port fail on my as this dongle catches on everything when I move the notebook in and out of my backpack. True story =(

Im experience this on both Ubuntu 16.04 and Kubuntu 18.04 on a XPS 13 9350 with latest BIOS
Mouse Im using is the Logitech 2S Anywhere or the 2S Master

Bluetooth coexistence has also come up in Bluetooth audio bug reports. However it's very much specific to the driver you're using. In particular, Qualcomm Atheros users please see bug 1746164.

If you're using a better supported Intel wifi/Bluetooth chip then I would expect it's not a driver problem but a local environmental problem with 2.4GHz interference, or just poor signal between the laptop and mouse. So you will need to do your own detective work there.

Broadcom chips, I'm not sure about their status but bug 1518408 is still open for them.

Finally, one tip: Close the Settings app before testing Bluetooth quality. While gnome-control-center is open and scanning for devices, it will impede Bluetooth signal quality (bug 1797002).