samples: wifi: provisioning: ble: Fix stack overflow

[D-Triveni]

Increase bluetooth RX stack size to prevent stack overflow.

Fixes SHEL-3623.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 1

Inputs:

Sources:

sdk-nrf: PR head: 72ec6f505b8f8d125e57729f840847029b820b16

more details

sdk-nrf:

PR head: 72ec6f505b8f8d125e57729f840847029b820b16
merge base: d0189a6959cded3ca35737a37359d2fde26b0fef
target head (main): d0189a6959cded3ca35737a37359d2fde26b0fef
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (1)

samples
│  ├── wifi
│  │  ├── provisioning
│  │  │  ├── ble
│  │  │  │  │ prj.conf

Outputs:

Toolchain

Version: 4aa3467a6d
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:4aa3467a6d_e85602c25f

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 7
• ❌ Integration tests
  • ❌ test-sdk-wifi

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-ps-main
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread-main
  • test-low-level
  • test-sdk-audio
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[krish2718]

I see max of 5120 in the NCS, so, a few queries:

1. What was the max usage?
2. Is this platform dependent?
3. Do we understand why the increase?
4. Do we need to update any other samples (not just Wi-Fi)

[D-Triveni]

@krish2718

1. Will check and update the PR with required maximum value.
2. No, we are seeing issue on all supported platforms.
3. Looks like the issue is seen after the recent upmerge.
4. No, the change is required only for this sample.

[krish2718]

Thanks, I guess !4 is more important to understand, why does this sample cause BT Rx thread stack to increase? IIUC, it should apply for any Wi-Fi/BLE combo case as the thread is part of HCI which is sample independent and I see no other sample bumping this.

[Copilot]

Pull Request Overview

This PR increases the Bluetooth RX stack size in the BLE provisioning sample to prevent stack overflow (SHEL-3623).

• Increased CONFIG_BT_RX_STACK_SIZE from 5120 to 5400 in the BLE WiFi provisioning sample.

[Copilot]

[nitpick] Add a comment explaining why the RX stack size was increased to 5400 (e.g., based on profiling or safe margins) to help future maintainers understand the rationale.

Suggested change

	# Increased RX stack size to 5400 based on profiling results to ensure sufficient buffer space for Bluetooth RX operations.