You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "rojer (via GitHub)" <gi...@apache.org> on 2024/12/23 14:05:46 UTC
[I] Host stuck in connecting state after timeout [mynewt-nimble]
rojer opened a new issue, #1948:
URL: https://github.com/apache/mynewt-nimble/issues/1948
Occasionally we get host stuck in a connecting state, where a connection that timed out has not been cleaned up.
In fact, in the post-mortem memory dump examination it looks exactly as the condition described in [this TODO](https://github.com/apache/mynewt-nimble/blob/895ed28b99080cef86828c3629fe53b4f80004e3/nimble/host/src/ble_gap.c#L2247-L2248): ble_gap_master.exp_set is 0, but cb and cb_arg are still set, suggesting that conn_complete never arrived.
If would be nice to have the remedial action implmeneted as described - an additional timeout and a controller reset.
FWIW, platform is ESP32-C3 with BLE_EXT_ADV enabled. And there's a suspicion that it only occurs when BLE_EXT_ADV is enabled, since it wasn't happening before.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@mynewt.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Host stuck in connecting state after timeout [mynewt-nimble]
Posted by "rojer (via GitHub)" <gi...@apache.org>.
rojer commented on issue #1948:
URL: https://github.com/apache/mynewt-nimble/issues/1948#issuecomment-2559776481
cc @ccollins476ad for context, maybe (blast from the past!)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@mynewt.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org