From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219387] Bluetooth: hci0: Reading supported features failed (-16)
Date: Tue, 28 Jan 2025 04:02:48 +0000 [thread overview]
Message-ID: <bug-219387-62941-PsFAfbo3dJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219387-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219387
--- Comment #11 from alexknoptech@protonmail.com ---
I thought this message came after the firmware file was already loaded:
```
[16265.746551] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[16265.753389] Bluetooth: hci0: Device revision is 5
[16265.753409] Bluetooth: hci0: Secure boot is enabled
[16265.753418] Bluetooth: hci0: OTP lock is enabled
[16265.753426] Bluetooth: hci0: API lock is enabled
[16265.753432] Bluetooth: hci0: Debug lock is disabled
[16265.753439] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[16265.765087] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[16267.499721] Bluetooth: hci0: Waiting for firmware download to complete
[16267.500335] Bluetooth: hci0: Firmware loaded in 1694653 usecs
[16267.500403] Bluetooth: hci0: Waiting for device to boot
[16267.512389] Bluetooth: hci0: Device booted in 11752 usecs
[16267.512396] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[16267.512498] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[16267.516460] Bluetooth: hci0: Applying Intel DDC parameters completed
[16267.517413] Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
>>>>[16267.519407] Bluetooth: hci0: Reading supported features failed (-16)
[16267.519423] Bluetooth: hci0: Error reading debug features
```
But also I am wondering if this log level can be changed to bt_dev_info if this
is not actually an issue, since the parent function simply returns that:
```
static int btintel_register_devcoredump_support(struct hci_dev *hdev)
{
struct intel_debug_features features;
int err;
FUNCTION CALLED HERE WHICH LOGS AT THE ERROR LEVEL>>>>
err = btintel_read_debug_features(hdev, &features);
if (err) {
bt_dev_info(hdev, "Error reading debug features");
return err;
}
if (!(features.page1[0] & 0x3f)) {
bt_dev_dbg(hdev, "Telemetry exception format not supported");
return -EOPNOTSUPP;
}
hci_devcd_register(hdev, btintel_coredump, btintel_dmp_hdr, NULL);
return err;
}
```
--
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-01-28 4:02 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 [this message]
2025-07-08 4:46 ` bugzilla-daemon
2025-12-24 15:04 ` bugzilla-daemon
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-PsFAfbo3dJ@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 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).