Ubuntu
linux package

BT mouse getting reset during operation

Bug #1796553 reported by Ralf Hildebrandt
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

(note: It's unclear to me if that's a kernel regression or an issue with bluez)

I've been using this particular combination of Bluetooth mouse ("TECKNET BM306") & laptop ("Dell Latitude E7240") for over a year now.

It used to work with 18.04 and 17.10, but with 18.10 I'm encountering a strange disconnect behaviour:

1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

when this happens, dmesg reports:

[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using ehci-pci

Disabling bluetooth and enabling it again results in:

[57833.455866] usb 1-1.3: USB disconnect, device number 18
[57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
[57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
[57837.016248] usb 1-1.3: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
[57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
[57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
[57841.724587] input: TECKNET BM306 Mouse as /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
[57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

$ bluetoothctl --version
bluetoothctl: 5.50

$ hciconfig -a
hci0: Type: Primary Bus: USB
 BD Address: FC:F8:AE:45:3C:05 ACL MTU: 1021:5 SCO MTU: 96:5
 UP RUNNING PSCAN
 RX bytes:52465 acl:3355 sco:0 events:222 errors:0
 TX bytes:28384 acl:13 sco:0 commands:170 errors:0
 Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF
 Link mode: SLAVE ACCEPT
 Name: 'ChromeLinux_AA14'
 Class: 0x0c010c
 Service Classes: Rendering, Capturing
 Device Class: Computer, Laptop
 HCI Version: 4.0 (0x6) Revision: 0x500
 LMP Version: 4.0 (0x6) Subversion: 0x500
 Manufacturer: Intel Corp. (2)

$ bluetoothctl
Agent registered
[TECKNET BM306]# show
Controller FC:F8:AE:45:3C:05 (public)
 Name: humbaba
 Alias: ChromeLinux_AA14
 Class: 0x000c010c
 Powered: yes
 Discoverable: no
 Pairable: yes
 UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
 UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
 UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
 UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
 UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
 UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v1D6Bp0246d0532
 Discovering: no
[TECKNET BM306]# devices
Device 20:9B:A5:68:AE:67 SoundBuds Flow
Device DC:2C:26:01:24:23 TECKNET BM306
Device 88:71:E5:0E:6B:99 Echo-HPT
Device 00:0B:E4:A0:A2:14 Nokia BH-103
Device A8:96:75:8B:4F:49 Moto G5S Plus
Device 00:02:5B:20:75:3C Trust SPK-02
Device 88:75:98:F2:5C:9E NS9+
Device 00:E0:4C:D5:E0:F5 SoundCore mini
[TECKNET BM306]# info DC:2C:26:01:24:23
Device DC:2C:26:01:24:23 (public)
 Name: TECKNET BM306
 Alias: TECKNET BM306
 Class: 0x00000580
 Icon: input-mouse
 Paired: yes
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
 UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
 UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
 Modalias: usb:v0A5Cp0001d0129

$ rfkill list
2: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
4: dell-wwan: Wireless WAN
 Soft blocked: yes
 Hard blocked: no
5: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
46: nfc0: NFC
 Soft blocked: no
 Hard blocked: no
48: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 7 12:05:36 2018
InstallationDate: Installed on 2014-02-07 (1702 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E7240
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (7 days ago)
dmi.bios.date: 02/01/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A25
dmi.board.asset.tag: humbaba
dmi.board.name: 0531FD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: humbaba
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA25:bd02/01/2018:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7240
dmi.product.sku: 05CA
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: FC:F8:AE:45:3C:05 ACL MTU: 1021:5 SCO MTU: 96:5
  UP RUNNING PSCAN
  RX bytes:126931 acl:8217 sco:0 events:414 errors:0
  TX bytes:28384 acl:13 sco:0 commands:170 errors:0

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It sounds more like a kernel issue (or hardware) if your Bluetooth dongle is getting reset:

[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using ehci-pci

so reassigning to the kernel.

Also, if your Bluetooth adapter is an external one then please try a different USB port.

no longer affects: bluez (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, according to your kernel log (CurrentDmesg.txt) the message happens along with a bunch of other messages relating to the system suspending/resuming. Maybe it is trying to suspend and just failed to do so?...

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Bluetooth adapter is builtin. so I can't change the port.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

It's definitely NOT happening while supending/resuming.
It happens while I'm using the machine, literally while moving the mouse.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

My next step is to test the upstream kernels, I guess?

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
In , caravena (caravena-linux-kernel-bugs) wrote :

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1796553

"(note: It's unclear to me if that's a kernel regression or an issue with bluez)

I've been using this particular combination of Bluetooth mouse ("TECKNET BM306") & laptop ("Dell Latitude E7240") for over a year now.

It used to work with 18.04 and 17.10, but with 18.10 I'm encountering a strange disconnect behaviour:

1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again."

Best regards,
--
Cristian Aravena Romero (caravena)

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Tested:

$ uname -a
Linux humbaba 4.19.0-041900rc7-generic #201810071631 SMP Sun Oct 7 16:33:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

and the error is still there.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

There's a new firmware for Intel 7260:
commit 70353356f8a01b6593ea94fd6ed6e9593fd0da1f
Author: Amit K Bag <email address hidden>
Date: Wed May 16 10:52:14 2018 +0530

    linux-firmware: Update firmware patch for Intel Bluetooth 7260 (B3/B4)

    This patch updates the firmware patch for Intel bluetooth 7260
    also known as Intel WP2 B3 and WP1 B4.

    Patch Version: 87

    Release Version: 20.60.0.2

Clone [1] and copy intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq to /lib/firmware/intel/.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

I cloned the repo and copied the new firmware to the appropriate place. Testing now.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Still the same issue.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Hello Ralf,

Execute the following command in the terminal:

$ ls -lihsa /lib/firmware/intel/

and paste what it returns here.

Best regards,
--
Cristian Aravena Romero (caravena)

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Download full text (4.5 KiB)

hildeb@humbaba:~$ ls -lihsa /lib/firmware/intel/
total 16M
3801225 12K drwxr-xr-x 2 root root 12K Sep 29 20:24 .
3801094 40K drwxr-xr-x 85 root root 36K Sep 29 20:25 ..
3817159 0 lrwxrwxrwx 1 root root 21 Aug 6 20:26 dsp_fw_bxtn.bin -> dsp_fw_bxtn_v3366.bin
3814817 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_bxtn_v2219.bin
3814818 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_bxtn_v3366.bin
3817161 0 lrwxrwxrwx 1 root root 20 Aug 6 20:26 dsp_fw_cnl.bin -> dsp_fw_cnl_v1191.bin
3814819 572K -rw-r--r-- 1 root root 571K Aug 6 20:26 dsp_fw_cnl_v1191.bin
3817163 0 lrwxrwxrwx 1 root root 20 Aug 6 20:26 dsp_fw_glk.bin -> dsp_fw_glk_v3366.bin
3814820 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_glk_v1814.bin
3814821 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_glk_v2768.bin
3814822 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_glk_v2880.bin
3814823 496K -rw-r--r-- 1 root root 494K Aug 6 20:26 dsp_fw_glk_v3366.bin
3817166 0 lrwxrwxrwx 1 root root 20 Aug 6 20:26 dsp_fw_kbl.bin -> dsp_fw_kbl_v3402.bin
3814824 236K -rw-r--r-- 1 root root 234K Nov 17 2017 dsp_fw_kbl_v1037.bin
3814825 236K -rw-r--r-- 1 root root 234K Aug 6 20:26 dsp_fw_kbl_v2042.bin
3814826 240K -rw-r--r-- 1 root root 238K Aug 6 20:26 dsp_fw_kbl_v2630.bin
3814827 240K -rw-r--r-- 1 root root 238K Aug 6 20:26 dsp_fw_kbl_v3266.bin
3814828 244K -rw-r--r-- 1 root root 242K Aug 6 20:26 dsp_fw_kbl_v3402.bin
3814829 240K -rw-r--r-- 1 root root 238K Aug 6 20:26 dsp_fw_kbl_v3420.bin
3814830 236K -rw-r--r-- 1 root root 234K Nov 17 2017 dsp_fw_kbl_v701.bin
3817169 0 lrwxrwxrwx 1 root root 24 Aug 6 20:26 dsp_fw_release.bin -> dsp_fw_release_v3402.bin
3814831 244K -rw-r--r-- 1 root root 242K Aug 6 20:26 dsp_fw_release_v3402.bin
3814832 216K -rw-r--r-- 1 root root 216K Aug 6 20:26 dsp_fw_release_v969.bin
3814833 688K -rw-r--r-- 1 root root 686K Aug 6 20:26 fw_sst_0f28.bin
3814834 260K -rw-r--r-- 1 root root 260K Mär 30 2017 fw_sst_0f28.bin-48kHz_i2s_master
3814835 688K -rw-r--r-- 1 root root 686K Aug 6 20:26 fw_sst_0f28_ssp0.bin
3814836 688K -rw-r--r-- 1 root root 686K Aug 6 20:26 fw_sst_22a8.bin
3814837 4,0K -rw-r--r-- 1 root root 18 Mär 5 2018 ibt-11-5.ddc
3814838 584K -rw-r--r-- 1 root root 581K Aug 30 21:57 ibt-11-5.sfi
3814839 4,0K -rw-r--r-- 1 root root 14 Aug 6 20:26 ibt-12-16.ddc
3814840 580K -rw-r--r-- 1 root root 579K Aug 30 21:57 ibt-12-16.sfi
3814841 4,0K -rw-r--r-- 1 root root 14 Apr 24 16:28 ibt-17-0-1.ddc
3814842 612K -rw-r--r-- 1 root root 611K Aug 6 20:26 ibt-17-0-1.sfi
3814903 4,0K -rw-r--r-- 1 root root 29 Aug 30 21:57 ibt-17-16-1.ddc
3814904 616K -rw-r--r-- 1 root root 614K Aug 30 21:57 ibt-17-16-1.sfi
3814843 4,0K -rw-r--r-- 1 root root 14 Apr 24 16:28 ibt-17-1.ddc
3814844 612K -rw-r--r-- 1 root root 611K Aug 6 20:26 ibt-17-1.sfi
3814905 4,0K -rw-r--r-- 1 root root 29 Aug 30 21:57 ibt-17-2.ddc
3814906 616K -rw-r--r-- 1 root root 614K Aug 30 21:57 ibt-17-2.sfi
3814907 4,0K -rw-r--r-- 1 root root 14 Apr 24 16:28 ibt-18-0-1.ddc
3814908 612K -rw-r--r-- 1 root root 611K Aug 6 20:26 ibt-18-0-1.sfi
3814911 4,0K -rw-r--r-- 1 root root 29 Aug 30...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try kernel parameter "btusb.enable_autosuspend=0".

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

btusb.enable_autosuspend=0 seems to have worked (so far)...

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

btusb.enable_autosuspend=0 definitely made the issue go away.

Bug Watch Updater (bug-watch-updater)
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Sorry for the belated response.

Please test if this kernel works for you, without using "btusb.enable_autosuspend=0":
https://people.canonical.com/~khfeng/lp1796553/

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Testing the kernel from https://people.canonical.com/~khfeng/lp1796553/
without btusb.enable_autosuspend=0

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

After a few days of testing (work, suspend, resume, work) it seem to work OK with the new kernel.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Now I'm on
linux-image-4.18.0-14-generic 4.18.0-14.15
(without btusb.enable_autosuspend=0) and it's broken again.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test this patch.

Ubuntu Foundations Team Bug Bot (crichton)
tags: added: patch
Brad Figg (brad-figg)
tags: added: ubuntu-certified
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.