https://bugzilla.kernel.org/show_bug.cgi?id=202515 Emil Lenngren (emil.lenngren@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emil.lenngren@xxxxxxxxx --- Comment #4 from Emil Lenngren (emil.lenngren@xxxxxxxxx) --- Command Disallowed does not mean unsupported hci command. "COMMAND DISALLOWED (0x0C) The Command Disallowed error code indicates that the command requested cannot be executed because the Controller is in a state where it cannot process this command at this time. This error shall not be used for command OpCodes where the error code Unknown HCI Command is valid." It's usually sent if the controller is busy with some operation which can't be combined with the one you're trying to execute. For example, some controllers only support either BLE scanning or BLE initiating at a time (exposed through LE Read Supported States). In that case, it will send Command Disallowed if scanning is already active. It could also be that you already have an active connection attempt outstanding, in that case it will also send Command Disallowed. You should use the new "btmon" tool which I assume supports decoding LE Extended Connect packets. Also try capture the packets before (ideally all the way from the hci is brought up) so one knows the whole state and can determine if we actually send a command that we are not allowed to in this state. -- You are receiving this mail because: You are the assignee for the bug.
