https://bugzilla.kernel.org/show_bug.cgi?id=215167 --- Comment #42 from Patrick Blesi (patrick.blesi@xxxxxxxxx) --- (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.
