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:45:43 +0000 [thread overview]
Message-ID: <bug-218416-62941-5J6OBtCkZH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218416
--- Comment #20 from Nickolas Gupton (nickolas@gupton.xyz) ---
I am on kernel 6.8.4 and using firmware 20242312, but Bluetooth is still not
working for me:
$ uname -a
Linux andromeda 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23
+0000 x86_64 GNU/Linux
$ journalctl -b | grep -E -i bluetooth
Apr 09 07:01:20 andromeda kernel: Bluetooth: Core ver 2.22
Apr 09 07:01:20 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI device and connection manager
initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: SCO socket layer initialized
Apr 09 07:01:21 andromeda systemd[1]: Reached target Bluetooth Support.
Apr 09 07:01:21 andromeda NetworkManager[794]: <info> [1712664081.1498] Loaded
device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Apr 09 07:01:23 andromeda kernel: 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-04-09 13:45 UTC|newest]
Thread overview: 26+ 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 [this message]
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
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-5J6OBtCkZH@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.