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: Wed, 12 Jul 2023 23:11:50 +0000	[thread overview]
Message-ID: <bug-216936-62941-hQFltOX1OV@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 #15 from espritlibre (espritlibre@yadim.dismail.de) ---
sorry! forget what i wrote, 5.19.11 seems to be bad too...

i think this could be a race condition between user space and kernel. because i
start my notbeook always in flight mode, in my case it's gnome/wayland. when i
turn off flight mode, the bluetooth firmware gets loaded.

if i turn flight mode off and quickly on again, so the firmware download gets
interrupted and results in a:
kernel: Bluetooth: hci0: FW download error recovery failed (-19)
most of the time

or:
kernel: Bluetooth: hci0: FW download error recovery failed (-108)

i think on boot, the kernel trys to upload the firmware and then the flight
mode kicks in, resulting in the error, sometimes. i need to pay more attention
and not use flight mode and see if the error appears again.

-- 
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-12 23:11 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 [this message]
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-hQFltOX1OV@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.