From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?)
Date: Fri, 12 Apr 2024 15:37:29 +0000 [thread overview]
Message-ID: <bug-216936-62941-on7439OWmw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216936
--- Comment #20 from Artem S. Tashkinov (aros@gmx.com) ---
This is still reproducible in 6.8.5:
dmesg -t | grep -i blue
Bluetooth: Core ver 2.22
NET: Registered PF_BLUETOOTH protocol family
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 173-5.24
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP socket layer initialized
Bluetooth: hci0: FW download error recovery failed (-19)
Bluetooth: hci0: sending frame failed (-19)
Bluetooth: hci0: Reading supported features failed (-19)
Bluetooth: hci0: Error reading debug features
Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not
supported.
Bluetooth: hci0: sending frame failed (-19)
Bluetooth: hci0: Failed to read MSFT supported features (-19)
Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
Bluetooth: hci0: Device revision is 2
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-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 173-5.24
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1129749 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 14839 usecs
Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware revision 0.1 build 173 week 5 2024
Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not
supported.
Bluetooth: MGMT ver 1.22
Bluetooth: ISO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
No timings, btintel just tries to load the firmware when it's already there (if
you're rebooting from Windows).
--
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:[~2024-04-12 15:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 20:35 [Bug 216936] New: [REGRESSION] The first attempt to upload firmware for Intel Bluetooth fails bugzilla-daemon
2023-01-15 20:38 ` [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?) bugzilla-daemon
2023-01-15 22:26 ` bugzilla-daemon
2023-01-16 12:42 ` bugzilla-daemon
2023-01-17 5:58 ` bugzilla-daemon
2023-01-31 3:01 ` bugzilla-daemon
2023-01-31 3:06 ` bugzilla-daemon
2023-01-31 9:11 ` bugzilla-daemon
2023-04-29 16:35 ` bugzilla-daemon
2023-04-30 8:44 ` bugzilla-daemon
2023-05-12 8:58 ` bugzilla-daemon
2023-05-13 10:59 ` bugzilla-daemon
2023-07-11 14:44 ` bugzilla-daemon
2023-07-11 14:48 ` bugzilla-daemon
2023-07-12 16:34 ` bugzilla-daemon
2023-07-12 23:11 ` bugzilla-daemon
2023-07-13 14:06 ` bugzilla-daemon
2023-07-29 20:09 ` bugzilla-daemon
2023-09-20 10:53 ` bugzilla-daemon
2023-09-24 10:11 ` bugzilla-daemon
2024-04-12 15:37 ` bugzilla-daemon [this message]
2024-04-12 19:56 ` bugzilla-daemon
2024-04-12 20:02 ` bugzilla-daemon
2024-04-12 21:40 ` bugzilla-daemon
2025-12-19 16:05 ` bugzilla-daemon
2025-12-19 22:10 ` bugzilla-daemon
2025-12-19 22:11 ` bugzilla-daemon
2025-12-19 22:22 ` bugzilla-daemon
2025-12-20 4:51 ` bugzilla-daemon
2025-12-20 5:00 ` bugzilla-daemon
2025-12-20 15:42 ` bugzilla-daemon
2025-12-20 20:41 ` bugzilla-daemon
2025-12-20 22:45 ` bugzilla-daemon
2025-12-22 15:41 ` bugzilla-daemon
2025-12-22 15:43 ` bugzilla-daemon
2025-12-23 15:16 ` bugzilla-daemon
2025-12-23 16:03 ` bugzilla-daemon
2025-12-24 15:43 ` bugzilla-daemon
2025-12-25 3:50 ` bugzilla-daemon
2025-12-25 9:32 ` 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-216936-62941-on7439OWmw@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).