Mailinglist Archive: opensuse-factory (765 mails)

< Previous Next >
Re: [opensuse-factory] Bluetooth keeps failing in Tumbleweed, including the current version 20171125, Linux 4.14.1-1-default #1 SMP PREEMPT
  • From: Knurpht - Gertjan Lettink <knurpht@xxxxxxxxxxxx>
  • Date: Wed, 29 Nov 2017 20:03:40 +0100
  • Message-id: <3546537.5P2f6e2oI3@knurpht-hp>
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
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 <oneukum@xxxxxxxx>
Sent: Wednesday, November 29, 2017 10:31 AM
To: Foolish Ewe; opensuse-factory@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups