Bluetooth Devices stop working after 30 sec to 1 minute

[Justin Ferguson]

Opening this bug per request in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389 ; I believe this is a continuation of that issue.

I'm continuing to experience the issue described in 1729389, despite that bug having been resolved. My Logitech Marathon 720 bluetooth mouse will work for 30 seconds to 1 minute after boot or resume from sleep, and then stop. Running `rfkill block bluetooth; rfkill unblock bluetooth` will get it working again until next reboot or sleep.

This is occurring using the latest kernel and latest linux-firmware on 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: jferg 2082 F...m pulseaudio
 /dev/snd/controlC0: jferg 2082 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 07:44:46 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b9745b4c-4441-456a-8591-e13c40dbb822
InstallationDate: Installed on 2017-10-15 (105 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 064e:3401 Suyin Corp.
 Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre x360 Convertible 13-ac0XX
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=55100938-c3ea-425a-a5f9-80e58b7b96f4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-17 (104 days ago)
dmi.bios.date: 04/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827E
dmi.board.vendor: HP
dmi.board.version: 94.60
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
dmi.sys.vendor: HP
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Dependencies:

DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-15 (105 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Package: linux-firmware 1.169.2
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: artful
Uname: Linux 4.15.0-041500-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to artful on 2017-10-17 (104 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Justin Ferguson (jferg)]

linux-firmware/artful-updates,artful-updates,now 1.169.2 all [installed,automatic]
  Firmware for Linux kernel drivers

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 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.15

[Justin Ferguson (jferg)]

Sorry, I guess that would be useful information.

It worked fine when I installed Ubuntu on the laptop sometime in October and updated to 17.10 from 17.04. Based on the kernels I have installed, that was at 4.13.7-041307-generic, but I /may/ be wrong on that - I may have been on an older kernel which is no longer on my disk.

In November, I did a dist-upgrade which took me to 4.13.0-17, where this behavior started, but I was able to work around it via a change I found via bug 1729389. (Unfortunately, I don't remember what the change was. I -think- it was adding bt_coex_active=0 for iwlwifi in /etc/modprobe.d/iwlwifi.conf.

Unfortunately, when I updated last week for SPECTRE/MELTDOWN (to 4.13.0-31 and 4.13.0-32), the workaround stopped working.

I will test the 4.15 kernel in a few.

[Justin Ferguson (jferg)]

apport information

[Justin Ferguson (jferg)]

apport information

[Justin Ferguson (jferg)]

This is not fixed in the mainline kernel.