ESP32 would reboot after running for ~3 days

[wwll123]

Hi,

I am running burn-in test for ESP32 with output log. All 4 modules would be rebooted after running for ~3 days with the same assertion error in log.c. Does anyone have any clue about this error?
Module: esp32-wrover-b
ESP-IDF: ESP-IDF v4.1

Error log:

Code: Select all

(292721597) AWS: Delta callback end
assertion "i == 0 || s_log_cache[(i - 1) / 2].generation < s_log_cache[i].generation" failed: file "/home/PC1/esp/esp-idf/components/log/log.c", line 209, function: get_cached_log_level
abort() was called at PC 0x400d7d3c on core 1

ELF file SHA256: 013e27b677f0aa2c

Backtrace: 0x400922e9:0x3ffdf7e0 0x40092685:0x3ffdf800 0x400d7d3c:0x3ffdf820 0x401d60d1:0x3ffdf850 0x40097edb:0x3ffdf880 0x401c7aed:0x3ffdf8d0 0x401c6a81:0x3ffdf900 0x401c6aca:0x3ffdf920 0x401c6d1b:0x3ffdf950 0x40094591:0x3ffdf990

Rebooting...

Thanks.

[ESP_Minatel]

Hi,

It looks something related to log cache. Are you using which log level?

[wwll123]

Hi,

It looks something related to log cache. Are you using which log level?

In menuconfig:
Bootloader log verbosity: Info
Default baud rate: 921600 bps
'idf.py' monitor baud rate: 921600 bps
UART console baud rate: 921600

In code:
All components are set to ERROR level.
One component is set to INFO level and others are DEBUG level.
AWS is DEBUG level. (most log is from AWS component)

I just don't know why all the devices would be rebooted after ~3 days with the same log.c error.

[ESP_Minatel]

Hi,

No clue about this issue.

I suggest you to open an issue on our GitHub: https://github.com/espressif/esp-idf/issues

Can you do that?

[ESP_Minatel]

Hi,

Any update on that?

[Senseless1972]

Got the same isse. Did you find a solution?