Bluetooth stops working when wifi is in use

[Jiří Janoušek]

Steps to reproduce:

1) Both Bluetooth & wifi is enabled in settings, but nothing is connected.
2) Connect a Bluetooth device, e.g., a mouse. It works.
3) Connect to a wifi network or create a wifi hotspot.

Expected result:

Both wifi and Bluetooth works, i.e., I can browse internet through the wifi connection, and my Bluetooth mouse still works.

Actual result:

- Wifi works, but the Bluetooth mouse stops working although it is still "connected" in Bluetooth settings.
- Any attempt to disconnect & reconnect the mouse fails.
- `systemctl restart Bluetooth` sometimes fails (see dmesg-hci-fail.txt), and then the system cannot be powered off

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-25-generic 4.13.0-25.29
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fenryxo 1999 F.... pulseaudio
CurrentDesktop: GNOME
Date: Thu Jan 18 11:34:44 2018
InstallationDate: Installed on 2018-01-10 (7 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 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 003: ID 04f2:b5e2 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 04f2:b5e1 Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre Laptop 13-af0xx
ProcFB:
 0 EFI VGA
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=e1e101f8-add8-4b5d-969d-c539be21e36f ro no_console_suspend initcall_debug resume=/dev/nvme0n1p3
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2018-01-10 (7 days ago)
dmi.bios.date: 10/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83A2
dmi.board.vendor: HP
dmi.board.version: 55.24
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre Laptop 13-af0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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

This change was made by a bot.

[Jiří Janoušek (fenryxo)]

Btw, if I use an external Bluetooth USD dongle, it still works when I connect to Wifi.

[Jiří Janoušek (fenryxo)]

The issue does not happen in Ubuntu 16.04 with kernel 4.10.0-28.

[Jiří Janoušek (fenryxo)]

Luckily, I still have kernel 4.10.0-19.21 from U17.04 available and it works ok with it in U17.10, which could suggest it is a kernel issue rather the user-space one.

Let me know if you need additional info or testing other kernel versions. I can live with 4.10.0-19.21 for now, but I'd rather have a supported kernel with the meltdown & spectre workarounds.

[Joseph Salisbury (jsalisbury)]

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-rc8

[Jiří Janoušek (fenryxo)]

4.15-rc8 fails
4.13rc1 fails
4.12.14 ok

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Jiří Janoušek (fenryxo)]

I was about to create an upstream report, but I cannot reproduce the issue with the newest mainline 4.16.0-041600-generic.

[Jiří Janoušek (fenryxo)]

I cannot reproduce with the latest Ubuntu kernel in Ubuntu 18.04.