-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth: controller: assert on conn update in slave role under max. throughput usecases #8796
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Milestone
Comments
@cvinayak is this something that will be resolved for 1.13? |
@nashif No, too close to the 1.13 release to reproduce, analyse and fix it, move it to 1.14. |
cvinayak
added a commit
to cvinayak/zephyr
that referenced
this issue
Nov 30, 2018
Explicitly track the connection update related ticker stop and start to avoid asserting due to ticker update being done at the same time for compensating the clock drift. The compensation related ticker update failure in this case can be safely ignored as new anchor point is used anyway at the instant of the connection update. Fixes zephyrproject-rtos#8796 Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
carlescufi
pushed a commit
that referenced
this issue
Dec 3, 2018
Explicitly track the connection update related ticker stop and start to avoid asserting due to ticker update being done at the same time for compensating the clock drift. The compensation related ticker update failure in this case can be safely ignored as new anchor point is used anyway at the instant of the connection update. Fixes #8796 Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
sjanc
pushed a commit
to sjanc/zephyr
that referenced
this issue
Jan 10, 2019
Explicitly track the connection update related ticker stop and start to avoid asserting due to ticker update being done at the same time for compensating the clock drift. The compensation related ticker update failure in this case can be safely ignored as new anchor point is used anyway at the instant of the connection update. Fixes zephyrproject-rtos#8796 Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
nashif
pushed a commit
that referenced
this issue
Jan 29, 2019
Explicitly track the connection update related ticker stop and start to avoid asserting due to ticker update being done at the same time for compensating the clock drift. The compensation related ticker update failure in this case can be safely ignored as new anchor point is used anyway at the instant of the connection update. Fixes #8796 Signed-off-by: Vinayak Kariappa Chettimada <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Bluetooth
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
This was reported under max. throughput usecases at 7.5ms conn intervals subjected to connection update procedures.
In slave role, ticker_update interface is used to compensate for clock drifts. ticker_stop and ticker_start interfaces are used to perform connection update. A race condition in the order of these calls is suspected to cause the assert.
A fix for this will be sent after a detailed analysis after a controlled reproduction of the said assert.
The text was updated successfully, but these errors were encountered: