Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-3406-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::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: Tue, 09 Apr 2024 19:57:44 +0000
Message-ID: <bug-218416-62941-vHJrJWYcuK@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

Warren Turkal (wt@penguintechs.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wt@penguintechs.org

--- Comment #24 from Warren Turkal (wt@penguintechs.org) ---
Does this have any relation to the message I am seeing in the journal logs
after warm boot? Namely this:

Bluetooth: hci0: command 0xfc00 tx timeout

I can confirm that I still get this message on a mainline kernel build.

I have started a thread on linux-bluetooth with the subject "QCA6390 blueto=
oth
doesn't work after warm boot or disable/reenable" if that helps.

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

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