[Solved] StoreProhibited sha engine?

[f.h-f.s.]

Hi all,

Lately we have seen this error occur. We have two running TLS connections using mbedtls.
Is this crash caused by both mbedtls connections requesting use of the SHA engine?

Code: Select all

Guru Meditation Error of type StoreProhibited occurred on core  0. Exception was unhandled.
Register dump:
0x40087dc9: uxListRemove at C:/IoT/BEASTv3/esp-idf/components/freertos/list.c:214
PC      : 0x40087dc9  PS      : 0x00060e33  A0      : 0x80086041  A1      : 0x3ffe8f40  
A2      : 0x3ffdcd40  A3      : 0x00060e23  A4      : 0x00060020  A5      : 0x00000000  
A6      : 0x00000000  A7      : 0x00000002  A8      : 0xff03104e  A9      : 0x02ac0f00  
A10     : 0x1edd0000  A11     : 0x3ffe90a0  A12     : 0x00000025  A13     : 0x0000000d  
A14     : 0x00000073  A15     : 0x00000025  SAR     : 0x00000010  EXCCAUSE: 0x0000001d  
0x4000c2e0: ?? ??:0
0x4000c2f6: ?? ??:0
EXCVADDR: 0x02ac0f08  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0x00000000  
0x40087dc9: uxListRemove at C:/IoT/BEASTv3/esp-idf/components/freertos/list.c:214
0x4008603e: xTaskPriorityDisinherit at C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4010
0x4008662e: prvCopyDataToQueue at C:/IoT/BEASTv3/esp-idf/components/freertos/queue.c:2034
0x4008693c: xQueueGenericSend at C:/IoT/BEASTv3/esp-idf/components/freertos/queue.c:2034
0x40081c11: lock_release_generic at C:/IoT/BEASTv3/esp-idf/components/newlib/locks.c:197
0x40081cb3: _lock_release at C:/IoT/BEASTv3/esp-idf/components/newlib/locks.c:203
0x401880be: esp_sha_unlock_engine at C:/IoT/BEASTv3/esp-idf/components/esp32/hwcrypto/sha.c:196
0x401734e4: mbedtls_sha512_finish at C:/IoT/BEASTv3/esp-idf/components/mbedtls/port/esp_sha512.c:394
0x40178dcd: sha384_finish_wrap at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/md_wrap.c:496
0x4016afe6: mbedtls_md_hmac_finish at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/md.c:138
0x4015f6a8: ssl_encrypt_buf at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/ssl_tls.c:6007
0x4015fc8d: mbedtls_ssl_write_record at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/ssl_tls.c:6007
0x40160a9d: ssl_write_real at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/ssl_tls.c:6007
0x40160af5: ssl_write_split at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/ssl_tls.c:6007
0x40160ba4: mbedtls_ssl_write at C:/IoT/BEASTv3/esp-idf/components/mbedtls/library/ssl_tls.c:6007
0x400ebd11: tlsio_mbedtls_send at C:/IoT/BEASTv3/components/azure_iot/tlsio_mbedtls.c:603
0x401895ef: xio_send at C:/IoT/BEASTv3/components/azure_iot/xio.c:150
0x400e7665: conn_send_all at C:/IoT/BEASTv3/components/azure_iot/httpapi_compact.c:46
0x400e7f39: SendHeadsToXIO at C:/IoT/BEASTv3/components/azure_iot/httpapi_compact.c:46
0x400e805a: HTTPAPI_ExecuteRequest at C:/IoT/BEASTv3/components/azure_iot/httpapi_compact.c:46
0x400e3303: _ZN14HttpClient_Api3GetEPKcP10BUFFER_TAGPj at C:/IoT/BEASTv3/main/HttpClient_Api.cpp:98
0x400e2a04: _ZN6BACAPI4PingEPKc at C:/IoT/BEASTv3/main/BACAPI.cpp:43
0x400e1a7e: _ZL7on_pingv at C:/IoT/BEASTv3/main/Main.cpp:430
0x400e309d: _ZN4Ping3NowEv at C:/IoT/BEASTv3/main/Ping.cpp:57
0x400e30ad: _ZN4Ping4TaskEPv at C:/IoT/BEASTv3/main/Ping.cpp:69 (discriminator 1)
Backtrace: 0x40087dc9:0x3ffe8f40 0x4008603e:0x3ffe8f60 0x4008662e:0x3ffe8f80 0x4008693c:0x3ffe8fa0 0x40081c11:0x3ffe8fe0 0x40081cb3:0x3ffe9010 0x401880be:0x3ffe9030 0x401734e4:0x3ffe9050 0x40178dcd:0x3ffe9080 0x4016afe6:0x3ffe90a0 0x4015f6a8:0x3ffe9100 0x4015fc8d:0x3ffe9170 0x40160a9d:0x3ffe91a0 0x40160af5:0x3ffe91d0 0x40160ba4:0x3ffe91f0 0x400ebd11:0x3ffe9210 0x401895ef:0x3ffe9230 0x400e7665:0x3ffe9250 0x400e7f39:0x3ffe9270 0x400e805a:0x3ffe96a0 0x400e3303:0x3ffe96e0 0x400e2a04:0x3ffe9720 0x400e1a7e:0x3ffe97a0 0x400e309d:0x3ffe97c0 0x400e30ad:0x3ffe97e0

[ESP_igrr]

What is the stack size of this ping task?

[f.h-f.s.]

The PingTask has 8 * 1024 bytes of stackspace, Priority: 02, StackHighWatermark: 4888 at runtime.
I should mention this problem does not always occur. This crash has occured 11 times since 6-6-2017.
9 times within 70000ms ( the ping task pings every 60seconds).
Two times after a long while (11h and one after 50minutes).

I also got a few assertions that failed

Code: Select all

C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
D (4667504) tlsio_mbedtls InitTask: tlsio_mbedtls_send
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
D (4667524) tlsio_mbedtls InitTask: tlsio_mbedtls_send
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
D (4667544) tlsio_mbedtls InitTask: tlsio_mbedtls_send
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
D (4667564) tlsio_mbedtls InitTask: tlsio_mbedtls_send
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
D (4667594) tlsio_mbedtls InitTask: tlsio_mbedtls_send
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!
C:/IoT/BEASTv3/esp-idf/components/freertos/tasks.c:4013 (xTaskPriorityDisinherit)- assert failed!

There are two tasks that use the same mbedtls connection. Which probably cause these crashes.