From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout
Date: Sat, 09 Apr 2022 22:06:31 +0000 [thread overview]
Message-ID: <bug-215167-62941-rTuyGPDKry@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215167-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215167
--- Comment #34 from Sergio Torres (sergiotca@gmail.com) ---
I believe I might be experiencing the same issue with my GIGABYTE B450 AORUS
PRO WIFI under Manajaro:
uname -r
>5.16.14-1-MANJARO
lsusb | grep -i bluetooth
>Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
sudo lsmod | grep bt
>btusb 65536 0
>btrtl 28672 1 btusb
>btbcm 24576 1 btusb
>btintel 45056 1 btusb
>bluetooth 770048 43 btrtl,btintel,btbcm,bnep,btusb,rfcomm
sudo dmesg | grep -i bluetooth
>[ 4.296518] Bluetooth: Core ver 2.22
>[ 4.296529] NET: Registered PF_BLUETOOTH protocol family
>[ 4.296530] Bluetooth: HCI device and connection manager initialized
>[ 4.296532] Bluetooth: HCI socket layer initialized
>[ 4.296533] Bluetooth: L2CAP socket layer initialized
>[ 4.296535] Bluetooth: SCO socket layer initialized
>[ 4.334693] Bluetooth: hci0: Legacy ROM 2.x revision 5.0 build 25 week 20
>2015
>[ 4.334695] Bluetooth: hci0: Intel device is already patched. patch num: 3c
>[ 4.405834] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>[ 4.405835] Bluetooth: BNEP filters: protocol multicast
>[ 4.405837] Bluetooth: BNEP socket layer initialized
>[ 16.384308] Bluetooth: RFCOMM TTY layer initialized
>[ 16.384314] Bluetooth: RFCOMM socket layer initialized
>[ 16.384317] Bluetooth: RFCOMM ver 1.11
>[ 18.557782] Bluetooth: hci0: command 0x0c24 tx timeout
>[ 20.691116] Bluetooth: hci0: command 0x0c52 tx timeout
Using rmmod btusb and modprobe btusb solves the issue for the rest of the
session.
--
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:[~2022-04-09 22:06 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 [this message]
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
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-rTuyGPDKry@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.