From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219387] Bluetooth: hci0: Reading supported features failed (-16)
Date: Wed, 24 Dec 2025 15:04:37 +0000 [thread overview]
Message-ID: <bug-219387-62941-YQd3ENijxx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219387-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219387
popy (tobias.diendorfer@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tobias.diendorfer@gmail.com
--- Comment #13 from popy (tobias.diendorfer@gmail.com) ---
Exact same issue here on EndavourOS (Arch) on kernel 6.18.2 with newest
linux-firmware-intel (currently 20251125-2).
here is the log:
[ 5239.185443] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 5239.190333] Bluetooth: hci0: Device revision is 5
[ 5239.190352] Bluetooth: hci0: Secure boot is enabled
[ 5239.190360] Bluetooth: hci0: OTP lock is enabled
[ 5239.190366] Bluetooth: hci0: API lock is enabled
[ 5239.190371] Bluetooth: hci0: Debug lock is disabled
[ 5239.190378] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5239.203072] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 5240.922007] Bluetooth: hci0: Waiting for firmware download to complete
[ 5240.923091] Bluetooth: hci0: Firmware loaded in 1679687 usecs
[ 5240.923135] Bluetooth: hci0: Waiting for device to boot
[ 5240.934911] Bluetooth: hci0: Device booted in 11535 usecs
[ 5240.934930] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[ 5240.938914] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 5240.940018] Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
[ 5240.941912] Bluetooth: hci0: Reading supported features failed (-16)
[ 5240.941917] Bluetooth: hci0: Error reading debug features
[ 5240.941925] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its
usage is not supported.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-12-24 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:40 [Bug 219387] New: Bluetooth: hci0: Reading supported features failed (-16) bugzilla-daemon
2024-10-14 16:42 ` [Bug 219387] " bugzilla-daemon
2024-10-16 5:51 ` bugzilla-daemon
2024-10-16 20:44 ` bugzilla-daemon
2024-10-16 21:02 ` bugzilla-daemon
2024-10-17 0:35 ` bugzilla-daemon
2024-11-03 14:04 ` bugzilla-daemon
2024-11-04 13:02 ` bugzilla-daemon
2024-11-04 13:04 ` bugzilla-daemon
2024-11-04 13:07 ` bugzilla-daemon
2025-01-27 19:02 ` bugzilla-daemon
2025-01-27 19:09 ` bugzilla-daemon
2025-01-28 4:02 ` bugzilla-daemon
2025-07-08 4:46 ` bugzilla-daemon
2025-12-24 15:04 ` bugzilla-daemon [this message]
2025-12-24 15:45 ` 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-219387-62941-YQd3ENijxx@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.