From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 190831] New: Intel Bluetooth 8260 breaks with latest firmware
Date: Wed, 21 Dec 2016 17:54:07 +0000 [thread overview]
Message-ID: <bug-190831-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=190831
Bug ID: 190831
Summary: Intel Bluetooth 8260 breaks with latest firmware
Product: Drivers
Version: 2.5
Kernel Version: 4.8.14
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: jan.steffens@gmail.com
Regression: No
My Bluetooth mouse only works for a few seconds (the exact time appears random)
after the Bluetooth controller is reset. At first, it seems only its "frame
rate" is reduced drastically, then it completely stops working. It also makes
pairing nearly impossible. "hciconfig hci0 reset" briefly gets the mouse
working again.
Firmware revision "0.0 build 95 week 37 2016" from linux-firmware 91ddce4
(built 2016-12-05) is broken. The driver boots with these messages:
Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Bluetooth: hci0: Device revision is 5
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1474407 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 10684 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)
Firmware revision "0.0 build 30 week 18 2016" from linux-firmware 9c71af9
(built 2016-10-05) works fine. The driver boots with these messages:
Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Bluetooth: hci0: Device revision is 5
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1555030 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 16567 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Setting Intel event mask failed (-16)
This problem seemed similar to
https://bugzilla.kernel.org/show_bug.cgi?id=189641 but the loss of function
doesn't correlate with any messages. However, while it is broken I do see the
occasional repeat of
Bluetooth: hci0 command 0x200c tx timeout
with varying command numbers.
As an aside, it appears the driver will only print the version if a firmware is
already loaded. This is a bit irritating as after a complete power-off (to
clear the firmware) btusb has to be unloaded and reloaded in order to print the
version.
Kernel is linux-zen 4.8.14 x86_64.
Hardware:
Intel Wireless 8260
Logitech MX Master
Downstream bug: https://bugs.archlinux.org/task/52214
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-12-21 17:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 17:54 bugzilla-daemon [this message]
2016-12-21 17:55 ` [Bug 190831] Intel Bluetooth 8260 breaks with latest firmware bugzilla-daemon
2016-12-21 18:08 ` bugzilla-daemon
2016-12-21 19:56 ` bugzilla-daemon
2016-12-21 20:23 ` bugzilla-daemon
2016-12-21 20:24 ` bugzilla-daemon
2016-12-22 6:49 ` bugzilla-daemon
2016-12-22 20:35 ` bugzilla-daemon
2016-12-23 9:16 ` bugzilla-daemon
2017-01-05 10:09 ` bugzilla-daemon
2017-01-05 13:14 ` bugzilla-daemon
2017-01-05 13:59 ` bugzilla-daemon
2017-01-05 14:44 ` bugzilla-daemon
2017-01-05 14:53 ` bugzilla-daemon
2017-01-06 6:19 ` bugzilla-daemon
2017-01-06 6:27 ` bugzilla-daemon
2017-01-06 6:28 ` bugzilla-daemon
2017-01-06 6:46 ` bugzilla-daemon
2017-01-06 6:59 ` bugzilla-daemon
2017-01-06 7:06 ` bugzilla-daemon
2017-01-06 7:27 ` bugzilla-daemon
2017-01-06 7:28 ` bugzilla-daemon
2017-01-06 8:00 ` bugzilla-daemon
2017-01-06 12:25 ` bugzilla-daemon
2017-01-08 10:46 ` bugzilla-daemon
2017-01-13 16:45 ` bugzilla-daemon
2017-01-15 16:43 ` bugzilla-daemon
2017-01-17 17:07 ` bugzilla-daemon
2017-01-17 17:08 ` bugzilla-daemon
2017-01-17 17:09 ` bugzilla-daemon
2017-01-18 13:49 ` bugzilla-daemon
2017-01-19 6:54 ` bugzilla-daemon
2017-01-19 6:54 ` bugzilla-daemon
2017-01-19 10:22 ` bugzilla-daemon
2017-01-19 10:31 ` bugzilla-daemon
2017-01-19 11:16 ` bugzilla-daemon
2017-01-20 13:21 ` bugzilla-daemon
2017-01-29 13:35 ` bugzilla-daemon
2017-01-31 0:34 ` bugzilla-daemon
2017-01-31 7:14 ` bugzilla-daemon
2017-01-31 18:31 ` bugzilla-daemon
2017-02-01 6:41 ` bugzilla-daemon
2017-02-01 13:24 ` bugzilla-daemon
2017-02-04 3:11 ` bugzilla-daemon
2017-02-09 6:48 ` bugzilla-daemon
2017-02-09 20:57 ` bugzilla-daemon
2017-02-11 15:24 ` bugzilla-daemon
2017-02-11 22:59 ` bugzilla-daemon
2017-02-18 20:43 ` bugzilla-daemon
2017-02-23 16:28 ` bugzilla-daemon
2017-02-23 16:39 ` bugzilla-daemon
2017-02-24 8:47 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-190831-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).