From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
Date: Mon, 25 Mar 2024 09:38:43 +0000 [thread overview]
Message-ID: <bug-218416-62941-vdNfRU8qrL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #8 from Jhon (vjstink@gmail.com) ---
(In reply to Nickolas Gupton from comment #7)
> Bluetooth is still not working on boot with kernel 6.7.9 with linux-firmware
> 20240220
> However, if I run this script (may take 2-3 runs sometimes) it will work:
>
> $ cat reset_bluetooth.sh
> modprobe -r btusb
> modprobe -r btintel
> sleep 2
> modprobe btintel
> modprobe btusb
> sleep 1
> systemctl restart bluetooth
Thanks for the script, it actually works after a couple of tries as you say,
really great.
I wonder, how did you enable these extra debug messages in journalctl? For
example, in mine it doesn't say anything about which firmware files it tries to
load.
I was trying to identify what it loads to replace them with some older versions
and see if I can make it work that way.
I also want to confirm again that the issue is still present in kernel 6.8.1
with the latest firmware update: 20240312
--
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:[~2024-03-25 9:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-24 23:39 ` [Bug 218416] " bugzilla-daemon
2024-01-30 14:21 ` bugzilla-daemon
2024-01-30 17:05 ` bugzilla-daemon
2024-02-04 10:31 ` bugzilla-daemon
2024-02-10 23:07 ` bugzilla-daemon
2024-02-11 20:32 ` bugzilla-daemon
2024-02-15 20:43 ` bugzilla-daemon
2024-03-09 16:52 ` bugzilla-daemon
2024-03-25 9:38 ` bugzilla-daemon [this message]
2024-03-29 8:52 ` bugzilla-daemon
2024-03-29 16:16 ` bugzilla-daemon
2024-03-29 18:31 ` bugzilla-daemon
2024-03-29 18:33 ` bugzilla-daemon
2024-03-29 20:02 ` bugzilla-daemon
2024-03-30 13:44 ` bugzilla-daemon
2024-04-03 12:32 ` bugzilla-daemon
2024-04-03 18:28 ` bugzilla-daemon
2024-04-04 22:50 ` bugzilla-daemon
2024-04-09 12:18 ` bugzilla-daemon
2024-04-09 13:04 ` bugzilla-daemon
2024-04-09 13:45 ` bugzilla-daemon
2024-04-09 13:46 ` bugzilla-daemon
2024-04-09 14:31 ` bugzilla-daemon
2024-04-09 15:12 ` bugzilla-daemon
2024-04-09 19:57 ` bugzilla-daemon
2024-05-23 14:54 ` bugzilla-daemon
2024-05-24 4:17 ` bugzilla-daemon
2024-05-24 15:29 ` bugzilla-daemon
2024-05-24 20:41 ` bugzilla-daemon
2024-05-24 21:01 ` bugzilla-daemon
2024-05-24 21:03 ` bugzilla-daemon
2024-05-24 21:11 ` bugzilla-daemon
2024-05-24 21:19 ` bugzilla-daemon
2024-05-25 5:22 ` bugzilla-daemon
2024-06-12 0:58 ` bugzilla-daemon
2024-06-12 1:06 ` bugzilla-daemon
2024-06-12 15:25 ` 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-218416-62941-vdNfRU8qrL@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).