All of lore.kernel.org
 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: Tue, 11 Jul 2023 14:44:08 +0000	[thread overview]
Message-ID: <bug-216936-62941-qsYg0T2B2v@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>

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

espritlibre (espritlibre@yadim.dismail.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |espritlibre@yadim.dismail.d
                   |                            |e

--- Comment #12 from espritlibre (espritlibre@yadim.dismail.de) ---
i have the same issue

Jul 11 16:06:56 kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio
is unblocked
Jul 11 16:06:57 kernel: Bluetooth: Core ver 2.22
Jul 11 16:06:57 kernel: NET: Registered PF_BLUETOOTH protocol family
Jul 11 16:06:57 kernel: Bluetooth: HCI device and connection manager
initialized
Jul 11 16:06:57 kernel: Bluetooth: HCI socket layer initialized
Jul 11 16:06:57 kernel: Bluetooth: L2CAP socket layer initialized
Jul 11 16:06:57 kernel: Bluetooth: SCO socket layer initialized
Jul 11 16:06:57 kernel: Bluetooth: hci0: Device revision is 0
Jul 11 16:06:57 kernel: Bluetooth: hci0: Secure boot is enabled
Jul 11 16:06:57 kernel: Bluetooth: hci0: OTP lock is enabled
Jul 11 16:06:57 kernel: Bluetooth: hci0: API lock is enabled
Jul 11 16:06:57 kernel: Bluetooth: hci0: Debug lock is disabled
Jul 11 16:06:57 kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jul 11 16:06:57 kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype
1 build 38
Jul 11 16:06:57 kernel: Bluetooth: hci0: Found device firmware:
intel/ibt-0040-0041.sfi
Jul 11 16:06:57 kernel: Bluetooth: hci0: Boot Address: 0x100800
Jul 11 16:06:57 kernel: Bluetooth: hci0: Firmware Version: 98-13.23
Jul 11 16:06:57 NetworkManager[1454]: <info>  [1689084417.8760] Loaded device
plugin: NMBluezManager
(/usr/lib/NetworkManager/1.42.6-1/libnm-device-plugin-bluetooth.so)
Jul 11 16:06:58 rfkill[1709]: block set for type bluetooth
Jul 11 16:06:58 systemd[1557]: Reached target Bluetooth.
Jul 11 16:06:58 kernel: Bluetooth: hci0: Failed to send firmware data (-19)
Jul 11 16:06:58 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 11 16:06:58 kernel: Bluetooth: hci0: FW download error recovery failed
(-19)
Jul 11 16:06:58 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 11 16:06:58 kernel: Bluetooth: hci0: Failed to read MSFT supported features
(-19)
Jul 11 16:06:58 systemd[1]: Starting Bluetooth service...
Jul 11 16:06:58 systemd[1557]: Stopped target Bluetooth.
Jul 11 16:06:58 bluetoothd[1842]: Bluetooth daemon 5.68
Jul 11 16:06:58 systemd[1]: Started Bluetooth service.
Jul 11 16:06:58 systemd[1]: Reached target Bluetooth Support.
Jul 11 16:06:58 systemd[1]: Stopped target Bluetooth Support.
Jul 11 16:06:58 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul 11 16:06:58 kernel: Bluetooth: BNEP filters: protocol multicast
Jul 11 16:06:58 kernel: Bluetooth: BNEP socket layer initialized
Jul 11 16:06:58 bluetoothd[1842]: Bluetooth management interface 1.22
initialized

i'm not exactly sure when this started happening but i can say it's at least
since kernel 6.1.x
i still have these errors on linux-hardened 6.1.38 and linux 6.4.2 and for me
it doesn't matter if they appear on a cold or warm boot, for example i can have
3 cold boots in a row without erros and on the fourth cold boot these errors
appear.
i can still connect my phone via bluetooth and send files to my phone and back,
when i have these errors but whenever i have these errors (most of the time)
turning bluetooth on most likely results in a kernel panic and i have to hard
power off the laptop which is fscking up my drive (sysrq/reisub ain't working)
my wifi card is AX211

i can try to bisect, if someone gives me instructions how to...

-- 
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:[~2023-07-11 14:44 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 [this message]
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-qsYg0T2B2v@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.