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 Jul 2023 20:09:18 +0000 [thread overview]
Message-ID: <bug-216936-62941-t0Cxx1oTyY@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 #17 from espritlibre (espritlibre@yadim.dismail.de) ---
sorry for getting back to this late and the confusion i caused, it's a busy
time... the kernels i use are arch kernel, according to the ArchWiki they are
pretty much vanilla upstream kernel with some patches applied, but for the
current kernel i'm running i see no patches in the PKGBUILD.
i have been observing journal in the and can say that even though i'm booting
without being in flightmode but wifi turned on, sometimes
> kernel: Bluetooth: hci0: Failed to send firmware data (-19)
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: FW download error recovery failed (-19)
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: Reading supported features failed (-19)
> kernel: Bluetooth: hci0: Error reading debug features
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
appears, or:
> kernel: Bluetooth: hci0: Failed to send firmware data (-19)
> kernel: Bluetooth: hci0: FW download error recovery failed (-108)
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: Reading supported features failed (-19)
> kernel: Bluetooth: hci0: Error reading debug features
> kernel: Bluetooth: hci0: sending frame failed (-19)
> kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
i played with bluetooth and the kernel didn't panic.
the last panic i got was 2 days ago and it went like this:
https://0x0.st/H2bz.txt (uploaded for better readability, no javascript needed)
i haven't tried 6.5-rc1, but yesterday i updated to linux-6.4.7.arch1-1. since
this bug is so annoying and they happen at random it's hard for me to bisect
and i'm not confident in saying kernel X is bad or good. i have set up kdump
now, which will automatically dump the crash. i hope this will lead to
something useful, i just booted the system 7-8 times but couldn't trigger a
panic.
--
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-07-29 20:09 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 [this message]
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-t0Cxx1oTyY@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.