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: Wed, 12 Jun 2024 00:58:04 +0000 [thread overview]
Message-ID: <bug-218416-62941-gVwO572gva@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Priit O. (priit@ww.ee) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |priit@ww.ee
--- Comment #34 from Priit O. (priit@ww.ee) ---
still present in kernel 6.9.3
dmesg | grep -i bluetooth
[ 4.466394] Bluetooth: Core ver 2.22
[ 4.466410] NET: Registered PF_BLUETOOTH protocol family
[ 4.466411] Bluetooth: HCI device and connection manager initialized
[ 4.466417] Bluetooth: HCI socket layer initialized
[ 4.466419] Bluetooth: L2CAP socket layer initialized
[ 4.466422] Bluetooth: SCO socket layer initialized
[ 5.405005] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.405007] Bluetooth: BNEP filters: protocol multicast
[ 5.405010] Bluetooth: BNEP socket layer initialized
[ 6.696883] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6.696966] Bluetooth: hci0: Reading Intel version command failed (-110)
what's even more troublesome is that previously I was able to make it work with
(sometimes with couple of tries):
sudo rmmod btusb && sudo modprobe btusb
now with this kernel I get only this over and over:
[ 74.101494] usbcore: deregistering interface driver btusb
[ 74.279683] usbcore: registered new interface driver btusb
[ 76.457250] Bluetooth: hci0: command 0xfc05 tx timeout
[ 76.457268] Bluetooth: hci0: Reading Intel version command failed (-110)
--
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-06-12 0:58 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
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 [this message]
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-gVwO572gva@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.