From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout
Date: Sun, 26 Feb 2023 23:14:02 +0000 [thread overview]
Message-ID: <bug-215167-62941-EyAkxZgeKU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215167-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215167
Chaim Eliyah (chaimeliyah@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chaimeliyah@gmail.com
--- Comment #46 from Chaim Eliyah (chaimeliyah@gmail.com) ---
+1 AX200
```
07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723]
(rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
```
```
[ 25.711840] Bluetooth: Core ver 2.22
[ 25.711860] NET: Registered PF_BLUETOOTH protocol family
[ 25.711861] Bluetooth: HCI device and connection manager initialized
[ 25.711864] Bluetooth: HCI socket layer initialized
[ 25.711866] Bluetooth: L2CAP socket layer initialized
[ 25.711869] Bluetooth: SCO socket layer initialized
[ 25.788390] iwlwifi 0000:07:00.0: loaded firmware version 66.f1c864e0.0
cc-a0-66.ucode op_mode iwlmvm
[ 27.783372] Bluetooth: hci0: command 0xfc05 tx timeout
[ 27.783378] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 28.785728] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 28.785731] Bluetooth: BNEP filters: protocol multicast
[ 28.785733] Bluetooth: BNEP socket layer initialized
```
```
celiyah@darkunicorn:~$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Sun 2023-02-26 16:43:43 CST; 12min ago
Docs: man:bluetoothd(8)
Main PID: 28973 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 76959)
Memory: 668.0K
CPU: 38ms
CGroup: /system.slice/bluetooth.service
└─28973 /usr/lib/bluetooth/bluetoothd
```
```
celiyah@darkunicorn:~$ bluetoothctl
Agent registered
[bluetooth]# scan on
No default controller available
quitetooth]#
```
It's popping up in Ubuntu forums e.g.
https://askubuntu.com/questions/1448731/bluetooth-not-working-no-controller-available
| Reloading `btusb` module several times makes it working.
Any specific steps for this? I have not been able to get it to work. Issue
persists despite reboots incl. hard power off/on. This happened suddenly.
```
celiyah@darkunicorn:~$ uname -a
Linux darkunicorn 5.15.0-56-lowlatency #62-Ubuntu SMP PREEMPT Wed Nov 23
09:50:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
celiyah@darkunicorn:~$ lsmod | grep bt
btusb 61440 0
btrtl 24576 1 btusb
btbcm 24576 1 btusb
btintel 40960 1 btusb
bluetooth 708608 12 btrtl,btintel,btbcm,bnep,btusb
```
(I believe the bleeding cutting edge 23.04.1 is the only available bunty
release with a 6 kernel line. Could be wrong.)
--
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:[~2023-02-26 23:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215167-62941@https.bugzilla.kernel.org/>
2021-11-29 18:07 ` [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout bugzilla-daemon
2021-11-29 21:50 ` bugzilla-daemon
2021-11-29 21:52 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:54 ` bugzilla-daemon
2021-11-29 21:58 ` bugzilla-daemon
2021-12-01 14:57 ` bugzilla-daemon
2021-12-05 7:05 ` bugzilla-daemon
2021-12-05 8:08 ` bugzilla-daemon
2021-12-11 12:39 ` bugzilla-daemon
2021-12-13 4:26 ` bugzilla-daemon
2021-12-13 4:26 ` bugzilla-daemon
2021-12-13 8:35 ` bugzilla-daemon
2022-02-09 8:48 ` bugzilla-daemon
2022-02-27 13:55 ` bugzilla-daemon
2022-03-14 11:14 ` bugzilla-daemon
2022-03-14 12:18 ` bugzilla-daemon
2022-03-15 13:54 ` bugzilla-daemon
2022-03-16 15:07 ` bugzilla-daemon
2022-04-06 7:18 ` bugzilla-daemon
2022-04-08 21:40 ` bugzilla-daemon
2022-04-09 22:06 ` bugzilla-daemon
2022-05-25 13:16 ` bugzilla-daemon
2022-05-25 13:44 ` bugzilla-daemon
2022-06-15 10:12 ` bugzilla-daemon
2022-06-15 11:17 ` bugzilla-daemon
2022-06-15 11:43 ` [Bug,215167] " bluez.test.bot
2022-06-30 14:16 ` [Bug 215167] " bugzilla-daemon
2022-08-18 15:03 ` bugzilla-daemon
2022-09-27 2:53 ` bugzilla-daemon
2022-09-29 0:49 ` bugzilla-daemon
2022-12-05 11:36 ` bugzilla-daemon
2022-12-28 15:18 ` bugzilla-daemon
2023-02-25 20:57 ` bugzilla-daemon
2023-02-26 23:14 ` bugzilla-daemon [this message]
2023-02-26 23:15 ` bugzilla-daemon
2023-02-26 23:59 ` bugzilla-daemon
2023-02-27 0:58 ` [Bug,215167] " bluez.test.bot
2023-04-21 7:31 ` [Bug 215167] " bugzilla-daemon
2023-04-29 7:37 ` bugzilla-daemon
2023-05-01 9:02 ` bugzilla-daemon
2023-07-09 6:18 ` bugzilla-daemon
2023-07-09 6:23 ` bugzilla-daemon
2023-09-08 11:59 ` bugzilla-daemon
2024-01-16 17:57 ` bugzilla-daemon
2024-01-17 10:38 ` bugzilla-daemon
2024-01-22 10:19 ` bugzilla-daemon
2024-05-25 5:11 ` bugzilla-daemon
2024-05-26 19:14 ` 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-215167-62941-EyAkxZgeKU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).