https://bugzilla.kernel.org/show_bug.cgi?id=215167 --- Comment #17 from Erik Rigtorp (erik@xxxxxxxxxx) --- (In reply to Takashi Iwai from comment #16) > When you add the BTUSB_INTEL_BROKEN_INITIAL_NCMD flag for your device > (8087:0aa7) in the blacklist_table[] in btusb.c as in comment 13, does it > fix the problem? Yes, running 5.15.16 tag from linux stable repo with this patch on top fixes the issue: diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index 79d0db542da3..0ed04061823b 100644 --- a/drivers/bluetooth/btusb.c +++ b/drivers/bluetooth/btusb.c @@ -368,7 +368,8 @@ static const struct usb_device_id blacklist_table[] = { BTUSB_INTEL_BROKEN_INITIAL_NCMD }, { USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL_COMBINED }, { USB_DEVICE(0x8087, 0x0a2b), .driver_info = BTUSB_INTEL_COMBINED }, - { USB_DEVICE(0x8087, 0x0aa7), .driver_info = BTUSB_INTEL_COMBINED }, + { USB_DEVICE(0x8087, 0x0aa7), .driver_info = BTUSB_INTEL_COMBINED | + BTUSB_INTEL_BROKEN_INITIAL_NCMD}, { USB_DEVICE(0x8087, 0x0aaa), .driver_info = BTUSB_INTEL_COMBINED }, /* Other Intel Bluetooth devices */ -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.