BLE Mesh Fast Prov - BT_OSI: osi_alarm_new alarm_cbs exhausted

I’m using ESP32-C3, ESP-IDF, and esp32-c3-devkitm-1. I run a project example fast prove server example and added the “Store BLE Mesh configuration persistently” to store the joining network data in NVS flash to the project.
my problem is after joining the node to the network (my client is nRF Mesh mobile App), everything is correct but when I reset the ESP32 and want to connect to it again the ESP32 reset. and I can not join ESP32 with nRF Mesh Mobile App.
the reset error is:

E (17862) BT_OSI: osi_alarm_new alarm_cbs exhausted
assert failed: hash_map_set hash_map.c:129 (data != NULL)
Core  0 register dump:
MEPC    : 0x403816be  RA      : 0x40389470  SP      : 0x3fcb6450  GP      : 0x3fc91000  
TP      : 0x3fc86b5c  T0      : 0x37363534  T1      : 0x7271706f  T2      : 0x33323130  
S0/FP   : 0x0000008e  S1      : 0x00000001  A0      : 0x3fcb648c  A1      : 0x3fc92a41  
A2      : 0x00000001  A3      : 0x00000029  A4      : 0x00000001  A5      : 0x3fc9d000  
A6      : 0x7a797877  A7      : 0x76757473  S2      : 0x00000009  S3      : 0x3fcb6599  
S4      : 0x3fc92a40  S5      : 0x3fcb687c  S6      : 0x00000000  S7      : 0x00000000  
S8      : 0x00000000  S9      : 0x00000000  S10     : 0x00000000  S11     : 0x00000000  
T3      : 0x6e6d6c6b  T4      : 0x6a696867  T5      : 0x66656463  T6      : 0x62613938  
MSTATUS : 0x00001881  MTVEC   : 0x40380001  MCAUSE  : 0x00000007  MTVAL   : 0x00000000  
MHARTID : 0x00000000  

Stack memory:
3fcb6450: 0x6e6d6c6b 0x6a696867 0x66656463 0x4038f1e2 0x3fc93298 0x3c0e4354 0x3fc93554 0x3c0e43d6
3fcb6470: 0x3fc932a8 0x3fcb6484 0x3fc932ac 0x3c0d4ecc 0x3fc92a40 0x00393231 0x3fca04d4 0x65737361
ELF file SHA256: 991d886fa7410010

Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xe (SPI_FAST_FLASH_BOOT)
Saved PC:0x403812e0
mode:DIO, clock div:1
entry 0x403cc710


Does anyone know why this error happens?

E (20204) BT_OSI: osi_alarm_new alarm_cbs exhausted

or how can solve it?
I see it when I enable the fast prove feature.
maybe it’s related to a config that I forget to set.

This seems to be very technical question about ESP-IDF, please try asking in ESP-IDF discussions (github) or their forum.

1 Like