Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-2978-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
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: Fri, 29 Mar 2024 18:33:21 +0000
Message-ID: <bug-218416-62941-sv2ZMcpO68@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 #12 from Gurenko Alex (agurenko@protonmail.com) ---
(In reply to Dustin from comment #11)
> (In reply to Gurenko Alex from comment #10)
> > (In reply to Olivier Delierre from comment #9)
> > > Had the same issue. Somehow, after a long power-off and turning on ag=
ain,
> > > Bluetooth managed to show up and the message was gone. Using an AX200=
 as
> > > well.
> > >=20
> > > Currently using kernel 6.8.2
> >=20
> > Wow, indeed, after upgrade powered off my desktop, flipped the PSU swit=
ch
> > for a few minutes and it worked on boot. This is very weird behavior.
>=20
> Sadly, its short lived. Mine stopped working again after the first resume
> from suspend that occurred after the cold boot.

Yes, same here, after normal reboot or shutdown (assuming it happens, becau=
se
it also hangs on shutdown/reboot now), it **only** works after PSU power cy=
cle

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

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