Bluetooth issues with Dell XPS 13 (9370)

[Felix Griewald]

I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled.

The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list.

To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying.

My syslog when this happens:

Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3
Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource
Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Default.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Startup finished in 15ms.
Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Shutdown.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Starting Exit the Session...
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Default.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Basic System.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Paths.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Timers.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Stopped target Sockets.
Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:46 visyu-albatross systemd[1]: [e-mail]: Start request repeated too quickly.
Apr 11 12:25:46 visyu-albatross systemd[1]: Failed to start User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[12140]: Received SIGRTMIN+24 from PID 12148 (kill).
Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c12 of user root.
Apr 11 12:25:46 visyu-albatross systemd[1]: Stopped User Manager for UID 0.
Apr 11 12:25:46 visyu-albatross systemd[1]: Removed slice User Slice of root.
Apr 11 12:25:47 visyu-albatross systemd[1]: Created slice User Slice of root.
Apr 11 12:25:47 visyu-albatross systemd[1]: Starting User Manager for UID 0...
Apr 11 12:25:47 visyu-albatross systemd[1]: Started Session c13 of user root.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Timers.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Sockets.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Paths.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Basic System.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Default.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Startup finished in 17ms.
Apr 11 12:25:47 visyu-albatross systemd[1]: Started User Manager for UID 0.
Apr 11 12:25:47 visyu-albatross systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopped target Bluetooth.
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
Apr 11 12:25:47 visyu-albatross systemd[12167]: Reached target Shutdown.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Default.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Basic System.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Timers.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Paths.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Stopped target Sockets.
Apr 11 12:25:47 visyu-albatross systemd[12167]: Starting Exit the Session...
Apr 11 12:25:47 visyu-albatross systemd[12167]: Received SIGRTMIN+24 from PID 12184 (kill).
Apr 11 12:25:47 visyu-albatross systemd[1]: Stopped User Manager for UID 0.
Apr 11 12:25:47 visyu-albatross systemd[1]: Removed slice User Slice of root.
Apr 11 12:25:48 visyu-albatross org.gnome.Terminal[2417]: ** (gnome-terminal-server:12197): WARNING **: Unable to set locale modifiers with XSetLocaleModifiers()

As far as I can see, it's the following hardware: QCA 6174 Killer Qualcomm / QCA 1535 Killer Qualcomm

Mostly I have these two bluetooth devices paired and connected:

- Logitech K810 keyboard
- Logitech MX Anywhere2 mouse

It's the default Ubuntu software configuration by Dell. Ubuntu 16.04, Kernel 4.4.0-121

If you need more information, please let me know.
---
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thunder 9273 F.... pulseaudio
CurrentDesktop: Unity
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8a49f47a-af59-4a45-9e33-fac6a66b8f97
InstallationDate: Installed on 2018-03-26 (29 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
MachineType: Dell Inc. XPS 13 9370
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic.efi.signed root=UUID=7c1e0890-7496-43db-b9d3-4cc7e38808d3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-121-generic N/A
 linux-backports-modules-4.4.0-121-generic N/A
 linux-firmware 1.173
Tags: xenial
Uname: Linux 4.4.0-121-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev rslsync sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 02/21/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9370
dmi.sys.vendor: Dell Inc.

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1766825

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[Felix Griewald (tiiunder)]

apport information

[James Turnbull (jamtur01)]

Also experiencing this issue. Same symptoms.

Some things we've tried and other folks impacted: https://www.dell.com/community/Linux-Developer-Systems/XPS-13-9370-no-bluetooth-after-suspend/td-p/6022892.

[Jared Dominguez (jared-dominguez)]

Thanks for reporting. I've reached out to have this LP bug looked at.

[Cyrus Lien (cyruslien)]

The kernel is 4.4.0-121-generic(#4), I though it was solved on kernel version >= 4.4.0-93.116.

[Cyrus Lien (cyruslien)]

@Felix,

Would you please try this issue on kernel 4.4.0-93.117 ?

[Cyrus Lien (cyruslien)]

@Felix,

Also, need more system information.
Please execute attached script by `sudo collect-log.sh' to collect more system information and attach debuglog.tgz here.

Thanks!

[Felix Griewald (tiiunder)]

@Cyrus

Here is the attached log collection.

Also I'm going to try kernel 4.4.0.93.116 (I didn't find 117 in the packages)

[Felix Griewald (tiiunder)]

Update: It's also happening with kernel 4.4.0-93.116

[Cyrus Lien (cyruslien)]

I can reproduce it only on AC mode. Still can reproduce it after disable tlp.

kernel: 4.4.0-100
BIOS: 1.2.1

[Cyrus Lien (cyruslien)]

A quick workaround is rmmod btusb before suspend and insert btusb after resume.
To do this, you can put a executable script of any name in /lib/systemd/system-sleep/.

Example:
#!/bin/sh

if [ "$1" = "pre" ]; then
  systemctl stop bluetooth && rmmod btusb
elif [ "$1" = "post" ]; then
  modprobe btusb && systemctl start bluetooth
fi

[Felix Griewald (tiiunder)]

Please take a look at this answer at AskUbuntu: https://askubuntu.com/a/1029749/95109

Using the newest driver files of the Windows driver and putting (overwriting) them into the /lib/firmware/qca directory seems to help. I'm using this for some days now and had no problems since then.

[Cyrus Lien (cyruslien)]

Confirmed, the issue was gone with firmware from https://askubuntu.com/a/1029749/95109.

[Cyrus Lien (cyruslien)]

Will escalate this issue to Qualcomm.

[Timo Jyrinki (timo-jyrinki)]

It seems there is no update since 2015 to qca subdir of linux-firmware, so those newer blobs will need to be submitted by Qualcomm, maybe ytkim specifically who did that 3 years ago if he's still at Qualcomm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/qca

[Sven Killig (sven-killig)]

Would be nice if someone from Qualcomm could have a look at it; just now an update of the linux-firmware Ubuntu package overwrote my fix again.

And I'm not sure if I got the right ramps_0x00000302_48.dfu
The Windows driver has these:
sonic@sonic-XPS-13-9370:/opt/Bluetooth_driver$ md5sum ramps*302*
067fb95e8501bad2683df07d23539e7d ramps_0x00000302_48.dfu
1028210a03cb116e8c482eb9cd263d39 ramps_0x00000302_48_NFA354A_10db.dfu
4b8012ca0a04e8061da510d3a5186852 ramps_TF_0x00000302_48.dfu
4b8012ca0a04e8061da510d3a5186852 ramps_TF_0x00000302_48_NFA435_10dbm.dfu
No idea what all these pre- and suffixes mean...

[Sven Killig (sven-killig)]

Sorry, I meant
> And I'm not sure if I got the right
nvm_usb_00000302.bin

[Rachel Greenham (rachel-strangenoises)]

I hid my earlier posts because I reckoned they were noise, tbh. This one less so. :-)

I have replaced the firmware files with those from the windows driver as described above and in the linked-to askubuntu. It worked brilliantly for a few days, no problems at all, but just now failed: Similar to what I found with btusb.enable_autosuspend=n, after one more sleep/wake cycle it came up with both bluetooth *and* wifi interfaces absent.

It does at least replicate my earlier findings, that now when it fails, it kills *both* interfaces, not just bluetooth. Maybe that points to a slightly different cause. And at least it does happen far less frequently. Still, the recovery remains to reboot into bios and switch both interfaces off and on again.

[zach (dunkirk)]

Cyrus Lien (cyruslien)'s solution works.

Just put a executable script of any name in /lib/systemd/system-sleep/.

#!/bin/sh

if [ "$1" = "pre" ]; then
  systemctl stop bluetooth && rmmod btusb
elif [ "$1" = "post" ]; then
  modprobe btusb && systemctl start bluetooth
fi

[Kai-Heng Feng (kaihengfeng)]

It's a dirty workaround. Is it possible for you to check if this issue still happen on Bionic/Cosmic?

[kao (kao1985)]

The issue affects also Cosmic (18.10)
Have
1) bluetooth missing
2) both wifi and bluetooth missing

[Kai-Heng Feng (kaihengfeng)]

kao,

Which wireless module does your XPS use?

[Anthony Wong (anthonywong)]

Qualcomm released new firmware recently that's worth checking out: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=534daf431c88b24236d23572039cdd79223b246a

[kao (kao1985)]

Kai-Heng Feng,
I have XPS 9370. It uses Killer 1435

Anthony Wong,
I've already tried. No success :( Still experiencing the same issue.

[kao (kao1985)]

Found something that can help. But it needs to be proved on 9370.
9360 has been added to btusb reset table right in kernel module.

https://patchwork.ozlabs.org/cover/926955/
https://github.com/torvalds/linux/blob/master/drivers/bluetooth/btusb.c

[Kai-Heng Feng (kaihengfeng)]

kao,

Please boot with kernel parameter "usbcore.dyndbg=+p" and attach dmesg after the issue happens.

[kao (kao1985)]

Proposed solution in #42 didn't help too.

Kai-Heng Feng,
Sure. Already added option and performed one sleep cycle. However, the issue hasn't occured still. It seems laptop should be in sleep mode for a number of hours.

[kao (kao1985)]

Kai-Heng Feng,
Please find the attached with dmesg. However, it's not pure bluetooth missing, I've lost both wifi and bluetooth. But think it has similar root.
Thank you

[Kai-Heng Feng (kaihengfeng)]

Kao, do you use preinstalled Ubuntu?
Also what you saw is not the same as the original bug, can you file a new bug instead?

[Cam Cope (ccope)]

I am also experiencing that both bluetooth and wifi are missing after setting mem_sleep to deep. My laptop also refuses to actually stay asleep in s2idle, I can see the screen come back on after I close the lid.

Ubuntu 18.04
Kernel 4.15.0-36-generic
XPS 9370

[Cam Cope (ccope)]

Attached more logs here. File contains dmesg for wifi crash, PCI device list and USB device list. Search for === to find section separators.

[Cam Cope (ccope)]

Also, I have to fully power off the laptop before booting again or else the devices won't come back (rebooting alone doesn't work).

[kao (kao1985)]

Kai-Heng Feng

Bluetooth missing issue started appearing again
dmesg attached

P.S. I use self-installed ubuntu 18.10

[spi (spi-gmxpro)]

I am on Ubuntu 18.04 with kernel 4.18.0-13-generic and still have the disappearing bluetooth issue. Reboot doesn't help, need to powercycle the XPS 9370.

[spi (spi-gmxpro)]

Forgot to mention: I only experinece this issue for the last few days. Didn't have this issue before and I've been using deep sleep from the beginning when I installed Ubuntu 18.04 myself. The only thing beside Ubuntu package updates that occured some days ago is a BIOS update to 1.6.3 on the XPS 9370.

[Alex Tu (alextu)]

iirc, the firmware has been upstreamed and landed to bionic.
Could someone who encounter this issue can have a try on latest kernel and firmware?

[Anthony Wong (anthonywong)]

In light of comment #54, I am setting the linux task of this bug to Incomplete for now, so that anyone who was hit by this bug can comment whether the issue still exist or not after performing a full system update on Bionic.

[Ellie Frost (stillinbeta)]

I'm running eoan and can confirm the issue with Bluetooth still exists on kernel 5.3.0-19-generic

[opensas (opensas)]

I can confirm that in ubuntu 18.04 the problem is still present

I just did a update && dist-upgrade

$ uname -a
Linux xps 4.15.0-1079-oem #89-Ubuntu SMP Fri Mar 27 05:22:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ sudo dmidecode | grep -A3 '^System Information'
System Information
 Manufacturer: Dell Inc.
 Product Name: XPS 13 9370
 Version: Not Specified

DO I have to send any other info to help fix this?

[opensas (opensas)]

BTW, just tried with this:

```
sudo add-apt-repository ppa:canonical-kernel-team/ppa
sudo apt-get update
sudo apt-get install linux-oem-osp1
```

which installed kernel

```
Linux xps 5.0.0-1050-oem-osp1 #55-Ubuntu SMP Fri Apr 24 11:08:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

```

And it seems to be working so far