Hello Holger: Thanks for the advice, I thought i was in compliance already with this (assuming that my file naming conventions are acceptable): $ cat /etc/modprobe.d/50-iwlwifi.conf options iwlwifi bt_coex_active=0 With best regards: Bill From: Holger Hetterich Sent: Wednesday, November 29, 2017 9:53 AM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT   On Intel chipset, please try adding: options iwlwifi bt_coex_active=0 to /etc/modprobe.d/iwlwifi.conf Regards, Holger Am 29.11.2017 um 09:47 schrieb Foolish Ewe:

Hello All:

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/"

https://www.opensuse.org/build/images/facebook-preview.jpg The makers' choice for sysadmins, developers and desktop ... www.opensuse.org Contribute Hardware. Donations to support the openSUSE project are always welcomed. In fact, Open Build Service, which is used by several other open-source projects ...

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.

With best regards:

Bill

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello Arjen: Sorry if this is redundant, the original reply attempt had html encoding so it might not have been delivered. I updated /etc/default/tlp as you suggested, however, I do not think that I have tlp enabled: $sudo tlp-stat -s [sudo] password for root: --- TLP 1.0 -------------------------------------------- +++ System Info System = HP HP Spectre x360 Convertible 15-bl1XX BIOS = F.20 Release = "openSUSE Tumbleweed" Kernel = 4.14.1-1-default #1 SMP PREEMPT Tue Nov 21 18:26:02 UTC 2017 (a5bca71) x86_64 /proc/cmdline = BOOT_IMAGE=/boot/vmlinuz-4.14.1-1-default root=UUID=27a1da0b-a162-4951-99ad-1bc3ca26e51d resume=/dev/disk/by-uuid/61a01547-7835-43ca-b6f0-eee7e2899883 splash=silent quiet showopts Init system = systemd v234 Boot mode = UEFI +++ TLP Status State = enabled Last run = 05:42:24 PM, 7832 sec(s) ago Mode = AC Power source = AC Notice: tlp.service is not enabled -- invoke "systemctl enable tlp.service" to correct this! Notice: tlp-sleep.service is not enabled -- invoke "systemctl enable tlp-sleep.service" to correct this! Notice: systemd-rfkill.service is not masked -- invoke "systemctl mask systemd-rfkill.service" to correct this! $ bluetooth bluetooth = on $ wifi wifi = on $ wwan wwan = none (no device) My bluetooth seemed well behaved, until this morning when I pulled my power cable to investigate if it was a power management issue. I lost bluetooth, rebooted and am waiting (with the power cable removed) to see if bluetooth again fails. With best regards: Bill From: Arjen de Korte Sent: Wednesday, November 29, 2017 6:31 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT   Citeren Foolish Ewe :

Hello Holger:

Thanks for the advice, I thought i was in compliance already with  this (assuming that my file naming conventions are acceptable):

$ cat /etc/modprobe.d/50-iwlwifi.conf options iwlwifi bt_coex_active=0

Do you have tlp enabled? I had endless amount of problems with my BT  mouse until I blacklisted BTUSB in /etc/default/tlp:      # Bluetooth devices are excluded from USB autosuspend:      #   0=do not exclude, 1=exclude      USB_BLACKLIST_BTUSB=1 The default as installed is 0.

With best regards:

Bill

From: Holger Hetterich Sent: Wednesday, November 29, 2017 9:53 AM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in  Tumbleweed, including the current version 20171125, Linux  4.14.1-1-default #1 SMP PREEMPT  

On Intel chipset, please try adding: options iwlwifi bt_coex_active=0

to /etc/modprobe.d/iwlwifi.conf

Regards, Holger

Am 29.11.2017 um 09:47 schrieb Foolish Ewe:

...

Hello All:

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/"

https://www.opensuse.org/build/images/facebook-preview.jpg The makers' choice for sysadmins, developers and desktop ... www.opensuse.org Contribute Hardware. Donations to support the openSUSE project are always welcomed. In fact, Open Build Service, which is used by several other open-source projects ...

  https://www.opensuse.org/build/images/facebook-preview.jpghttps://www.opensu...

The makers' choice for sysadmins, developers and desktop ... www.opensuse.org Contribute Hardware. Donations to support the openSUSE project are  always welcomed. In fact, Open Build Service, which is used by  several other open-source projects ...

...

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.

With best regards:

Bill

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello Oliver: Thanks for your advice, we are now tracking this now on https://bugzilla.opensuse.org/show_bug.cgi?id=1070434. Regarding bisecting the kernel, have been running Linux on this machine with unstable bluetooth since October 21, 2017, the machine's specs per the vendor are  https://support.hp.com/us-en/document/c05787871. Is bisection supposed to isolate the transition from broken to fixed (or vice versa if we have a regression). If all states are broken, how will I bisect? 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. HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product. 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. With best regards: Bill From: Oliver Neukum Sent: Wednesday, November 29, 2017 10:31 AM To: Foolish Ewe; opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT   Am Mittwoch, den 29.11.2017, 08:47 +0000 schrieb Foolish Ewe:

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.

Your XHCI is failing catastrophically. The failure of Bluetooth is among the expected consequences. The best way to debug this is to bisect the kernel. Could you do that? And please make a bugzilla entry for such issues.         Regards                 Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello Knurpht: Thanks for the kind suggestion, I did update the /etc/default/tlp setting as you suggested, but I don't think tlp is enabled on my system: $sudo tlp-stat -s [sudo] password for root: --- TLP 1.0 -------------------------------------------- +++ System Info System = HP HP Spectre x360 Convertible 15-bl1XX BIOS = F.20 Release = "openSUSE Tumbleweed" Kernel = 4.14.1-1-default #1 SMP PREEMPT Tue Nov 21 18:26:02 UTC 2017 (a5bca71) x86_64 /proc/cmdline = BOOT_IMAGE=/boot/vmlinuz-4.14.1-1-default root=UUID=27a1da0b-a162-4951-99ad-1bc3ca26e51d resume=/dev/disk/by-uuid/61a01547-7835-43ca-b6f0-eee7e2899883 splash=silent quiet showopts Init system = systemd v234 Boot mode = UEFI +++ TLP Status State = enabled Last run = 05:42:24 PM, 7832 sec(s) ago Mode = AC Power source = AC Notice: tlp.service is not enabled -- invoke "systemctl enable tlp.service" to correct this! Notice: tlp-sleep.service is not enabled -- invoke "systemctl enable tlp-sleep.service" to correct this! Notice: systemd-rfkill.service is not masked -- invoke "systemctl mask systemd-rfkill.service" to correct this! $ bluetooth bluetooth = on $ wifi wifi = on $ wwan wwan = none (no device) Your hint sounded plausible initially, but now I'm skeptical that tlp was the culprit. With best regards: Bill From: Knurpht - Gertjan Lettink Sent: Wednesday, November 29, 2017 7:03 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT   Op woensdag 29 november 2017 19:50:52 CET schreef Foolish Ewe:

Hello Oliver:

Thanks for your advice, we are now tracking this now on https://bugzilla.opensuse.org/show_bug.cgi?id=1070434.

Regarding bisecting the kernel,  have been running Linux on this machine with unstable bluetooth since October 21, 2017, the machine's specs per the vendor are  https://support.hp.com/us-en/document/c05787871. Is bisection

HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product.

supposed to isolate the transition from broken to fixed (or vice versa if we have a regression). If all states are broken, how will I bisect?  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

en:users:drivers:iwlwifi [Linux Wireless] wireless.wiki.kernel.org iwlwifi is the wireless driver for Intel's current wireless chips. For older chips, there are other drivers:

chipset), motivating me to try tumbleweed.

HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product.

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.

With best regards:

Bill

From: Oliver Neukum Sent: Wednesday, November 29, 2017 10:31 AM To: Foolish Ewe; opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT

Am Mittwoch, den 29.11.2017, 08:47 +0000 schrieb Foolish Ewe:

...

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. Your XHCI is failing catastrophically. The failure of Bluetooth is among the expected consequences. The best way to debug this is to bisect the kernel. Could you do that? And please make a bugzilla entry for such issues.

         Regards                  Oliver What I needed to get bluetooth back working on TW on my HP laptop: Setting BLACKLIST_BTUSB to 1 in /etc/default/tlp Using rfkill to unblock the BT device.

-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello Knurpht: I had my laptop charging overnight and bluetooth did not fail, but as an experiment I removed the charging cable and the bluetooth went out shorty afterwards, so perhaps you and Arjen are on to something? I've rebooted since, while plugged in I see. Before pulling the power cable I saw: $ sudo rfkill list [sudo] password for root: 0: phy0: Wireless LAN         Soft blocked: no         Hard blocked: no 5: hci0: Bluetooth         Soft blocked: no         Hard blocked: no After unplugging my charging cable, my bluetooth went down, I think this is the relevant logs. 2017-11-29T10:14:01.641618-08:00 linux kernel: [ 7876.205632] EDD information not available. 2017-11-29T12:12:26.413620-08:00 linux kernel: [14980.975944] acpi INT3400:00: Unsupported event [0x86] 2017-11-30T08:01:44.585659-08:00 linux kernel: [86339.143271] acpi INT3400:00: Unsupported event [0x86] 2017-11-30T08:01:45.433568-08:00 linux kernel: [86339.992199] acpi INT3400:00: Unsupported event [0x86] 2017-11-30T08:07:04.630451-08:00 linux kernel: [86659.188990] xhci_hcd 0000:00:14.0: xHC is not running. 2017-11-30T08:07:14.442642-08:00 linux kernel: [86669.001225] xhci_hcd 0000:00:14.0: xHC is not running. 2017-11-30T08:07:49.126513-08:00 linux kernel: [86703.685052] xhci_hcd 0000:00:14.0: xHC is not running. 2017-11-30T08:07:49.137656-08:00 linux kernel: [86703.692238] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead 2017-11-30T08:07:49.137715-08:00 linux kernel: [86703.692245] xhci_hcd 0000:00:14.0: HC died; cleaning up 2017-11-30T08:07:49.189653-08:00 linux kernel: [86703.745132] usb 1-5: USB disconnect, device number 2 2017-11-30T08:07:49.189726-08:00 linux kernel: [86703.746303] usb 1-7: USB disconnect, device number 3 I forgot to repeat the rfkill list command after losing bluetooth :-(. I am repeating the experiment and pulled the power cable again, but was not able to replicate the failure (I don't remember if the failure only happened when on battery, or if it also happened when charging). I see that my KDE sessions' Battery and Brightness has has "Enable Power Management" enabled, I am not sure how that is activated. I did not notice anything that seemed bluetooth specific there. With best regards: Bill From: Knurpht - Gertjan Lettink Sent: Thursday, November 30, 2017 12:46 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT   Op donderdag 30 november 2017 05:06:25 CET schreef Foolish Ewe:

Hello Knurpht:

Thanks for the kind suggestion, I did update the /etc/default/tlp setting as you suggested, but I don't think tlp is enabled on my system:

$sudo tlp-stat -s [sudo] password for root: --- TLP 1.0 --------------------------------------------

+++ System Info System         = HP   HP Spectre x360 Convertible 15-bl1XX BIOS           = F.20 Release        = "openSUSE Tumbleweed" Kernel         = 4.14.1-1-default #1 SMP PREEMPT Tue Nov 21 18:26:02 UTC 2017 (a5bca71) x86_64 /proc/cmdline  = BOOT_IMAGE=/boot/vmlinuz-4.14.1-1-default root=UUID=27a1da0b-a162-4951-99ad-1bc3ca26e51d resume=/dev/disk/by-uuid/61a01547-7835-43ca-b6f0-eee7e2899883 splash=silent quiet showopts Init system    = systemd v234 Boot mode      = UEFI

+++ TLP Status State          = enabled Last run       = 05:42:24 PM,   7832 sec(s) ago Mode           = AC Power source   = AC

Notice: tlp.service is not enabled -- invoke "systemctl enable tlp.service" to correct this! Notice: tlp-sleep.service is not enabled -- invoke "systemctl enable tlp-sleep.service" to correct this! Notice: systemd-rfkill.service is not masked -- invoke "systemctl mask systemd-rfkill.service" to correct this!

$ bluetooth bluetooth = on $ wifi wifi      = on $ wwan wwan      = none (no device)

Your hint sounded plausible initially, but now I'm skeptical that tlp was the culprit.

With best regards:

Bill

From: Knurpht - Gertjan Lettink Sent: Wednesday, November 29, 2017 7:03 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT

Op woensdag 29 november 2017 19:50:52 CET schreef Foolish Ewe:

...

Hello Oliver:

Thanks for your advice, we are now tracking this now on https://bugzilla.opensuse.org/show_bug.cgi?id=1070434.

Regarding bisecting the kernel,  have been running Linux on this machine with unstable bluetooth since October 21, 2017, the machine's specs per the vendor are  https://support.hp.com/us-en/document/c05787871. Is bisection

HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product.

HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product.

...

supposed to isolate the transition from broken to fixed (or vice versa if we have a regression). If all states are broken, how will I bisect?  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

en:users:drivers:iwlwifi [Linux Wireless] wireless.wiki.kernel.org iwlwifi is the wireless driver for Intel's current wireless chips. For older chips, there are other drivers:

en:users:drivers:iwlwifi [Linux Wireless] wireless.wiki.kernel.org

iwlwifi is the wireless driver for Intel's current wireless chips. For older

chips, there are other drivers:

...

chipset), motivating me to try tumbleweed.

HP Spectre x360 - 15-bl112dx Product Specifications | HP ... support.hp.com Looking for upgrade or update information? Trying to find the names of components or programs? This document contains the technical details for this product.

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.

With best regards:

Bill

From: Oliver Neukum Sent: Wednesday, November 29, 2017 10:31 AM To: Foolish Ewe; opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT

Am Mittwoch, den 29.11.2017, 08:47 +0000 schrieb Foolish Ewe:

...

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.

Your XHCI is failing catastrophically. The failure of Bluetooth is among the expected consequences. The best way to debug this is to bisect the kernel. Could you do that? And please make a bugzilla entry for such issues.

         Regards                  Oliver

What I needed to get bluetooth back working on TW on my HP laptop: Setting BLACKLIST_BTUSB to 1 in /etc/default/tlp Using rfkill to unblock the BT device. AFAIK tlp gets started by something else.

What does rfkill list say ? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org