Blueooth: Controller Response COMMAND DISALLOWED

[LingaoM]

Describe the bug

Use nrf52832 as controller, use nrf52840 as host, use H4 transport layer.

*** Booting Zephyr OS build zephyr-v2.4.0-1367-g7d16ab50d738 **

[00:00:02.807,769] bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:02.807,800] bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:02.807,800] bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.4 Build 99
[00:00:02.825,592] bt_hci_core: Identity: e4:0c:5e:e9:04:9a (random)
[00:00:02.825,592] bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:02.825,622] bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:09.433,471] bt_mesh_health_cli.health_cli_init: primary 1
[00:00:09.433,776] bt_mesh_prov_device: Device UUID: 3a2b2d51-f1a3-47ad-bb49-7c23c85219b3
[00:00:09.438,903] bt_hci_core: opcode 0x200b status 0x0c
[00:00:09.438,903] bt_mesh_adv: starting scan failed (err -5)

I did not modify any code in the host or controller. This problem occurs from time to time. However, if the host and controller are in the same chip, the problem is not found.

[cvinayak]

Please provide details to reproduce like the commit, samples, configuration, build steps used, flashing steps and test procedure.

[carlescufi]

@LingaoM could you please pinpoint the exact HCI command that is getting command disallowed? This could be the set random address one, which would be different from what you analyzed.
EDIT: This is actually failing on Set Scan Parameters, so this looks like a bug in the Host itself, not Mesh or the Controller.