Linux-Bluetooth Archive on
 help / color / Atom feed
Subject: [Bug 202515] Bluetooth LE Extended Connect returning Command Disallowed
Date: Wed, 06 Feb 2019 09:42:10 +0000
Message-ID: <> (raw)
In-Reply-To: <>

Emil Lenngren ( changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #4 from Emil Lenngren ( ---
Command Disallowed does not mean unsupported hci command.

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

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.

  parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  0:01 [Bug 202515] New: " bugzilla-daemon
2019-02-06  8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06  8:27 ` bugzilla-daemon
2019-02-06  9:07 ` bugzilla-daemon
2019-02-06  9:42 ` bugzilla-daemon [this message]
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:19 ` bugzilla-daemon
2019-02-06 11:58 ` bugzilla-daemon
2019-02-06 12:18 ` bugzilla-daemon
2019-02-06 19:36 ` bugzilla-daemon
2019-02-07 12:59 ` bugzilla-daemon
2019-02-07 22:55 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-07 23:48 ` bugzilla-daemon
2019-02-08 16:16 ` bugzilla-daemon
2019-02-08 17:35 ` bugzilla-daemon
2019-02-08 21:39 ` bugzilla-daemon

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox