https://bugzilla.kernel.org/show_bug.cgi?id=202515 Bug ID: 202515 Summary: Bluetooth LE Extended Connect returning Command Disallowed Product: Drivers Version: 2.5 Kernel Version: v4.19 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Bluetooth Assignee: linux-bluetooth@xxxxxxxxxxxxxxx Reporter: master.homer@xxxxxxxxx Regression: No Ever since Linux v4.19 I haven't been able to connect to my mouse via bluetooth LE, using an Intel 9260 (supporting AC Wifi and Bluetooth 5) with a pci-e adaptor. Basically, the device doesn't pair at all - dmesg just says: Bluetooth: hci0: request failed to create LE connection: status 0x0c. I've been able to narrow this down to commit 4d94f95d30c8fbfe86068e9abed110974d697cf5, which introduced extended LE Connect if supported by the card. To get some more info, I ran hcidump, and the relevant output says: < HCI Command: Unknown (0x08|0x0043) plen 26 > HCI Event: Command Status (0x0f) plen 4 Unknown (0x08|0x0043) status 0x0c ncmd 1 Error: Command Disallowed On a working system (using v4.18), with the legacy connect command, the hcidump says: < HCI Command: LE Create Connection (0x08|0x000d) plen 25 bdaddr DA:B8:DC:90:75:A7 type 1 interval 96 window 96 initiator_filter 0 own_bdaddr_type 0 min_interval 6 max_interval 9 latency 100 supervision_to 600 min_ce 0 max_ce 0 > HCI Event: Command Status (0x0f) plen 4 LE Create Connection (0x08|0x000d) status 0x00 ncmd 2 I also grabbed the Local commands supported, which says: < HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0 > HCI Event: Command Complete (0x0e) plen 68 Read Local Supported Commands (0x04|0x0002) ncmd 1 status 0x00 Commands: fffffb03ccffefffff3ffc9ff30fe8fe3ff78fff1c00040061f7ffff7fb80000 feffffffffdfff07 As far as I can see, the kernel checks byte 37 of the local supported commands output, to see if it should enable the Extended connect command or not. I couldn't find any reports at all about this, and I couldn't really find much info on the extended connect command at all. Is there any way of disabling this? Or would it be at all possible to use the legacy connect command when the extended command fails? Do let me know if you need any more information. -- You are receiving this mail because: You are the assignee for the bug.
