Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-3381-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
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: Tue, 09 Apr 2024 13:04:42 +0000
Message-ID: <bug-218416-62941-NL8Abnv9kl@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 #19 from Olivier Delierre (contact@odelierre.fr) ---
(In reply to Jugoslav Gacas from comment #18)
> The issue has been fixed for me after upgrading to kernel 6.8.4-arch1-1 on
> Arch-linux.

Can confirm. Upgraded kernel to 6.8.4-arch1-1, removed btusb from the module
loading blacklist, powered-off the PC and powering it on again, bluetooth w=
as
working.

Tried several things such as rebooting, rebooting on my Windows drive,
rebooting to Archlinux again, powering-off: no power-off hanging, and bluet=
ooth
was working immediately after each start-up, without having to deal with
modprobe anyhow.

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

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