Bug ID 1070434
Summary Bluetooth/USB keeps failing in Tumbleweed in intel 8265 Bluetooth + Wifi and intel Sunrise Point-LP USB-3.0 xHCI Controller, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Factory
Status NEW
Severity Major
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter foolishewe@hotmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Hello All:

I have been running Linux on this machine with unstable bluetooth
since October 21, 2017, and bluetooth keeps failing after working for some
reasonably long period (minutes or hours, possibly due to usb issues).

The machine's specs per the vendor are 
https://support.hp.com/us-en/document/c05787871. 
The hardware is pretty new hence the need for a new kernel
(4.6+ according to https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
ofr intel 8265 chipset),
motivating me to try tumbleweed.

The wlan and bluetooth chip according to the linux drivers is:
4.830236] iwlwifi 0000:3b:00.0: Detected Intel(R) Dual Band Wireless AC 8265,
REV=0x230

I dual boot into windows and the bluetooth seems reliable under windows, so I
am ruling out hardware issues.
On a side note, I put Bumblebee on this system last night (tainting my kernel) 
to address screen flicker, but the bluetooth issue predates that, the logs
attached are prior to the installation of bumblebee.

I am using opensuse tumbleweed for the last 6 weeks or so and keep having my
bluetooth support fail while I'm using my laptop.  I'm currently up to date (as
of a few hours ago):

$uname -a
Linux linux 4.14.1-1-default #1 SMP PREEMPT Tue Nov 21 18:26:02 UTC 2017
(a5bca71) x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20171125"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="20171125"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20171125"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"

Consider the following log, I think bluetooth failed around 21:53:54, what
could be going on here?  Is this an usb error or bluetooth specific?  What
information do I need to track this down?
$journalctl -all
[Stuff removed for brevity]

Nov 28 21:39:08 linux dbus[1126]: [system] Successfully activated service
'org.kde.powerdevil.backlighthelper'
Nov 28 21:39:18 linux systemd[1]: Starting Cleanup of Temporary Directories...
Nov 28 21:39:18 linux systemd[1]: Started Cleanup of Temporary Directories.
Nov 28 21:41:51 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:43:39 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:44:20 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:47:20 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:47:28 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:52:04 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:53:54 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 21:53:54 linux kernel: xhci_hcd 0000:00:14.0: xHCI host controller not
responding, assume dead
Nov 28 21:53:54 linux kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 28 21:53:54 linux kernel: usb 1-5: USB disconnect, device number 2
Nov 28 21:53:54 linux kernel: usb 1-7: USB disconnect, device number 3
Nov 28 21:53:54 linux systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 28 21:53:54 linux systemd[1]: bluetooth.target: Unit not needed anymore.
Stopping.
Nov 28 21:53:54 linux systemd[1]: Stopped target Bluetooth.
Nov 28 21:53:54 linux systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 28 21:53:54 linux bluetoothd[1117]: Endpoint unregistered: sender=:1.39
path=/MediaEndpoint/A2DPSource
Nov 28 21:53:54 linux bluetoothd[1117]: Endpoint unregistered: sender=:1.39
path=/MediaEndpoint/A2DPSink
Nov 28 21:53:54 linux dbus[1126]: [system] Rejected send message, 1 matched
rules; type="error", sender=":1.39" (uid=1000 pid=2094
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)"
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented"
requested_reply="0" destination=":1.1" (uid=0 pid=1117
comm="/usr/lib/bluetooth/bluetoothd ")
Nov 28 21:53:54 linux dbus[1126]: [system] Rejected send message, 1 matched
rules; type="error", sender=":1.39" (uid=1000 pid=2094
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)"
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented"
requested_reply="0" destination=":1.1" (uid=0 pid=1117
comm="/usr/lib/bluetooth/bluetoothd ")
Nov 28 21:53:54 linux dbus[1126]: [system] Rejected send message, 1 matched
rules; type="error", sender=":1.39" (uid=1000 pid=2094
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)"
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented"
requested_reply="0" destination=":1.1" (uid=0 pid=1117
comm="/usr/lib/bluetooth/bluetoothd ")
Nov 28 21:53:54 linux dbus[1126]: [system] Rejected send message, 1 matched
rules; type="error", sender=":1.39" (uid=1000 pid=2094
comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)"
member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented"
requested_reply="0" destination=":1.1" (uid=0 pid=1117
comm="/usr/lib/bluetooth/bluetoothd ")

After a reboot, I bluetooth failed pretty quickly, I see:
ov 28 22:02:44 linux nm-dispatcher[2752]: req:2 'connectivity-change': start
running ordered scripts...
Nov 28 22:02:51 linux PackageKit[2580]: daemon quit
Nov 28 22:02:51 linux packagekitd[2580]: Source ID 11 was not found when
attempting to remove it
Nov 28 22:02:57 linux kernel: xhci_hcd 0000:00:14.0: xHC is not running.
Nov 28 22:02:57 linux kernel: xhci_hcd 0000:00:14.0: xHCI host controller not
responding, assume dead
Nov 28 22:02:57 linux kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 28 22:02:57 linux kernel: usb 1-5: USB disconnect, device number 2
Nov 28 22:02:57 linux kernel: usb 1-7: USB disconnect, device number 3
Nov 28 22:02:57 linux systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 28 22:02:57 linux systemd[1]: bluetooth.target: Unit not needed anymore.
Stopping.
Nov 28 22:02:57 linux systemd[1]: Stopped target Bluetooth.

What information would help to track down and fix this problem?

Thanks:

Bill


You are receiving this mail because: