Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting for once, to make this easily accessible to everyone. CCing a few lists and people. Greg is among them, who might know if this is a known issue that 6.6.4-rc1 et. al. might already fix. If that is not the case I guess we might need a bisection between 6.6.1 and 6.6.2 know if mainline is affected might be good, too. Cioa, Thorsten On 01.12.23 02:54, Kris Karas (Bug Reporting) wrote: > > With mainline kernel 6.6.2+ (and 6.1.63, etc), bluetooth is inoperative > (reports "opcode 0x0c03 failed") on my motherboard's bluetooth adapter > (Intel chipset). Details below. > > I reported this in a comment tacked onto bugzilla #218142, but got no > response, so posting here as a possibly new issue. > > Details, original email: > ---------------------------------------------------------------------- > I have a regression going from mainline kernel 6.1.62 to 6.1.63, and > also from kernel 6.6.1 to 6.6.2; I can bisect if patch authors can't > locate the relevant commit. In the most recent kernels mentioned, > bluetooth won't function. > > Hardware: ASRock "X470 Taichi" motherboard - on board chipset. > lsusb: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth. > dmesg: Bluetooth: hci0: Legacy ROM 2.x revision 5.0 build 25 week 20 2015 > Bluetooth: hci0: Intel Bluetooth firmware file: > intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq > Bluetooth: hci0: Intel BT fw patch 0x43 completed & activated > bluez: Version 5.70, bluez firmware version 1.2 > Linux kernel firmware: 20231117_7124ce3 > > On a working kernel (such as 6.6.1), in addition to the dmesg output > above, we have this: > dmesg: Bluetooth: MGMT ver 1.22 > Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0) > > On a failed kernel (such as 6.6.2), instead of the good output above, we > have: > dmesg: Bluetooth: hci0: Opcode 0x0c03 failed: -110 > Bluetooth: hci0: Opcode 0x0c03 failed: -110 > ... > repeats several times as bluez attempts to communicate with hci0. > ---------------------------------------------------------------------- > > Since that email was sent, kernel firmware has been updated to > 20231128_aae6052, and kernels 6.1.64 and 6.6.3 have been tried with no > change observed. > > Kris
