linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, 19 Dec 2025 16:05:03 +0000	[thread overview]
Message-ID: <bug-216936-62941-zxyqFx3ZQW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216936

cheako+kernel_org@mikemestnik.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cheako+kernel_org@mikemestn
                   |                            |ik.net

--- Comment #24 from cheako+kernel_org@mikemestnik.net ---
My testing shows that cold/worm boot is a red herring, the issue is random and
if you do it one way enough times you may well find you can get *both* states.

@Mario what were you thinking for DD?  For me this happens while going
multiuser, so I really would like kernel cmdline or `/etc`/`initramfs` setting
and not echoing things on a prompt.

I added this to `~/.config/autostart/xmessage.desktop`
```desktop
[Desktop Entry]
Type=Application
Exec=sh -c 'sudo dmesg|grep hci0|xmessage -file -'
Hidden=false
X-GNOME-Autostart-enabled=true
Name[en_US]=xmessage
Name=xmessage
Comment[en_US]=xmessage preformance monitoring
Comment=xmessage preformance monitoring
```

I get either no hci0 logs, xmsg is empty, or this:
```dmsg
[    9.536622] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[    9.540760] Bluetooth: hci0: Device revision is 1
[    9.540766] Bluetooth: hci0: Secure boot is enabled
[    9.540769] Bluetooth: hci0: OTP lock is enabled
[    9.540771] Bluetooth: hci0: API lock is enabled
[    9.540773] Bluetooth: hci0: Debug lock is disabled
[    9.540775] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    9.544653] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    9.544681] Bluetooth: hci0: Boot Address: 0x24800
[    9.544684] Bluetooth: hci0: Firmware Version: 193-33.24
[   10.058240] Bluetooth: hci0: Failed to send firmware data (-19)
[   10.058266] Bluetooth: hci0: sending frame failed (-19)
[   10.058276] Bluetooth: hci0: FW download error recovery failed (-19)
[   10.058313] Bluetooth: hci0: sending frame failed (-19)
[   10.058319] Bluetooth: hci0: Reading supported features failed (-19)
[   10.058322] Bluetooth: hci0: Error reading debug features
[   10.058328] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its
usage is not supported.
[   10.058342] Bluetooth: hci0: sending frame failed (-19)
[   10.058349] Bluetooth: hci0: Failed to read MSFT supported features (-19)
```

I had been using BT for a few months, so suddenly loosing it after a kernel
upgrade really sucks!

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2025-12-19 16:05 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
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 [this message]
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-zxyqFx3ZQW@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).