Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-2719-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
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
Message-ID: <bug-218416-62941-vdNfRU8qrL@https.bugzilla.kernel.org/>
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>
References: <bug-218416-62941@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0

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

--- 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-firmw=
are
> 20240220
> However, if I run this script (may take 2-3 runs sometimes) it will work:
>=20
> $ cat reset_bluetooth.sh=20
> 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 trie=
s to
load.
I was trying to identify what it loads to replace them with some older vers=
ions
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

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

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