[v1.14] Bluetooth: thread crashes when configuring a non 0 Slave Latency #32430
Assignees
Labels
area: Bluetooth Controller
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
LTS
Long term release branch related
priority: high
High impact/importance bug
Projects
Milestone
Comments
cvinayak
added
area: Bluetooth
area: Bluetooth Controller
LTS
carlescufi
changed the title
cvinayak
added a commit
to cvinayak/zephyr
that referenced
this issue
Feb 23, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Relates to zephyrproject-rtos#32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
carlescufi
pushed a commit
that referenced
this issue
Feb 23, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Relates to #32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
cvinayak
added a commit
to cvinayak/zephyr
that referenced
this issue
Apr 6, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Relates to zephyrproject-rtos#32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
carlescufi
pushed a commit
that referenced
this issue
Apr 13, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Relates to #32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
cvinayak
added a commit
to cvinayak/zephyr
that referenced
this issue
Apr 14, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Fixes zephyrproject-rtos#32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
|
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
nashif
pushed a commit
that referenced
this issue
May 21, 2021
When ticker job is disabled inside radio events then all advertising, scanning, and slave latency cancel ticker operations will be deferred, requiring increased ticker thread context operation queue count. Fixes #32430. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Our nRF52 peripheral device running Zephyr v1.14 accepts up to 4 connections from central devices (CONFIG_BT_MAX_CONN = 4), all go well with the default BT_PERIPHERAL_PREF_SLAVE_LATENCY = 0 config.
If we change BT_PERIPHERAL_PREF_SLAVE_LATENCY to non 0, and make 3 or above connections, the bluetooth thread crashes within minutes.
To Reproduce
CONFIG_BT_MAX_CONN = 4
BT_PERIPHERAL_PREF_SLAVE_LATENCY = 2
Expected behavior
No crash of threads.
Impact
Major
Logs and console output
[00:05:33.008,941] bt_ctlr_ctrl: assert: '(ticker_status == 0) || (ticker_status == 2)' failed
***** Kernel OOPS! *****
Current thread ID = 0x200028f4
Faulting instruction address = 0x266e6
Fatal fault in thread 0x200028f4! Aborting.
Environment (please complete the following information):
Additional context
Reported to @cvinayak on Slack.
The text was updated successfully, but these errors were encountered: