From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215167] Bluetooth: hci0: command 0xfc05 tx timeout
Date: Thu, 29 Sep 2022 00:49:35 +0000 [thread overview]
Message-ID: <bug-215167-62941-WCuaHSs7Vl@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 #42 from Patrick Blesi (patrick.blesi@gmail.com) ---
(In reply to Patrick Blesi from comment #41)
> I am experiencing the same problem with 5.15.67 for USB Device
> USB_DEVICE(0x8087, 0x0aaa).
>
> ~ $ uname -a
> Linux a0d7b954-ssh 5.15.67 #1 SMP Tue Sep 13 13:54:38 UTC 2022 x86_64 Linux
>
> ~ $ lsusb
> Bus 001 Device 001: ID 1d6b:0002
> Bus 001 Device 003: ID 1043:8012
> Bus 002 Device 001: ID 1d6b:0003
> Bus 001 Device 002: ID 8087:0aaa
>
> ~ $ dmesg | grep -i bluetooth
> [ 0.454719] Bluetooth: Core ver 2.22
> [ 0.454904] NET: Registered PF_BLUETOOTH protocol family
> [ 0.455504] Bluetooth: HCI device and connection manager initialized
> [ 0.455896] Bluetooth: HCI socket layer initialized
> [ 0.456392] Bluetooth: L2CAP socket layer initialized
> [ 0.456894] Bluetooth: SCO socket layer initialized
> [ 4.452912] Bluetooth: hci0: Reading Intel version command failed (-110)
> [ 4.452955] Bluetooth: hci0: command 0xfc05 tx timeout
> [ 4.498402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 4.498405] Bluetooth: BNEP filters: protocol multicast
> [ 4.498409] Bluetooth: BNEP socket layer initialized
This was actually a red herring. The issue was manifested by not connecting my
Bluetooth PCI devices as a passthrough to my lxd virtual machine. To resolve I
removed the Bluetooth USB device (0x8087, 0x0aaa) and added the PCI controller
and shared RAM PCI controller in the same iommu group.
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
--
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-09-29 0:51 UTC|newest]
Thread overview: 48+ 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 [this message]
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
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-WCuaHSs7Vl@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).