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: Sat, 29 Apr 2023 16:35:30 +0000 [thread overview]
Message-ID: <bug-216936-62941-HRxQIpzMhw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216936
James Addison (jay+bko@jp-hosting.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jay+bko@jp-hosting.net
--- Comment #8 from James Addison (jay+bko@jp-hosting.net) ---
I'm seeing a similar problem intermittently, since at least 6.1.0 of the
kernel.
Hardware: Intel Corporation Wireless 8260 [8086:24f3]
(yes, it reads like the name a wi-fi card, but it does also contain a bluetooth
controller)
Here are the oldest relevant logs that I have available:
Mar 23 21:19:13 kernel: Linux version 6.1.0-6-amd64
(debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU
Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.15-1 (2023-03-05)
...
Mar 23 21:19:14 kernel: usb 1-7: USB disconnect, device number 2
Mar 23 21:19:14 kernel: Bluetooth: hci0: Failed to send firmware data (-19)
Mar 23 21:19:14 kernel: Bluetooth: hci0: sending frame failed (-19)
Mar 23 21:19:14 kernel: Bluetooth: hci0: FW download error recovery failed
(-19)
The logs contain 165 occurrences of "hci0: Waiting for firmware download to
complete", and 9 occurrences of "hci0: FW download error recovery failed".
I'm not yet sure whether there's a specific series of actions to recreate the
failure.
--
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:[~2023-04-29 16:35 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 [this message]
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
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-HRxQIpzMhw@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).