Task watchdog got triggered with WiFi and Bluetooth in the same time

[fly135]

BTW, it bears noting that when recommending people to enable WD panic, also advise to think about the time period. Doing something as standard as OTA will cause your app to crash if you leave it at the default.

John A

[davdav]

Hi @fly135

But it's starting to look like I'm going to need to set up the IDF watchdog to handle this is wifi task hanging disables esp_restart. I'm not convinced it does though. The reason being that when the wifi task hung in my app it appeared that the APP core was still working.

I confirm that APP core is correclty running.Moreover "esp_restart" doesn't work when

Code: Select all

Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE

starts appearing. What I observe is that some tasks are "killed" (for example a task which reads from UART) but others are working (for a example a task which controls I2C). I do not pinmed any task to a specific core, so what I'm guessing is that esp_restart stop the task on a core but the other is stuck due to "wifi" exception.

In my case the Task watchdog triggered started in this way

Code: Select all

I (6068961) wifi: bcn_timout,ap_probe_send_start
I (6071465) wifi: ap_probe_send over, resett wifi status to disassoc
I (6071465) wifi: state: run -> init (100)
I (6071466) wifi: pm stop, total sleep time: 2811620671 us / 6072922354 us

I (6071471) wifi: n:7 0, o:7 2, ap:255 255, sta:7 2, prof:1
Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE

And available heap was around 43000bytes so I don't think it's a problem of RAM. I'm working on esp-v3.1 release (22da5f) BUT esp32/lib component is updated to latest commit (05aa0f4).

[davdav]

I would like also to reference this issue on github which is related to this topic.

https://github.com/espressif/esp-idf/issues/2370