wifi:ieee80211_ioctl.c 1443

[ChrisAlfred]

I am using IDF v4,2 with nimble and AWS IoT
When I do large large number of MQTT submits< randomly get the error:
"E (7213995) wifi:ieee80211_ioctl.c 1443"

As a result, the MQTT publish aws_iot_mqtt_publish never returns.

ieee80211_ioctl.c is closed source.

What does this error mean?
What are the possible causes?

[AshUK_]

Also seeing this on v4.3-beta-2 and it never kicks the WDT resulting in a reset.

Code: Select all

E (9107264) wifi:ieee80211_ioctl.c 1443
E (9112261) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (9112261) task_wdt:  - IDLE (CPU 0)
E (9112261) task_wdt: Tasks currently running:
E (9112261) task_wdt: CPU 0: wifi
E (9112261) task_wdt: CPU 1: IDLE
E (9112261) task_wdt: Aborting.

abort() was called at PC 0x40159e8c on core 0
0x40159e8c: task_wdt_isr at /Users/ash/dev/esp/esp-idf-latest-release/components/esp_common/src/task_wdt.c:182 (discriminator 1)
Backtrace:0x40090517:0x3ffbe470 0x40090dcd:0x3ffbe490 0x40098549:0x3ffbe4b0 0x40159e8c:0x3ffbe530 0x40082ab1:0x3ffbe550 0x401cbb9b:0x3ffdf5b0 0x401cc0b2:0x3ffdf5d0 0x401cc568:0x3ffdf600 0x401cbacd:0x3ffdf620 0x401cbb2e:0x3ffdf640 0x4009a0b2:0x3ffdf660 0x40092c6a:0x3ffdf690
0x40090517: panic_abort at /Users/ash/dev/esp/esp-idf-latest-release/components/esp_system/panic.c:356
0x40090dcd: esp_system_abort at /Users/ash/dev/esp/esp-idf-latest-release/components/esp_system/system_api.c:112
0x40098549: abort at /Users/ash/dev/esp/esp-idf-latest-release/components/newlib/abort.c:46
0x40159e8c: task_wdt_isr at /Users/ash/dev/esp/esp-idf-latest-release/components/esp_common/src/task_wdt.c:182 (discriminator 1)
0x40082ab1: _xt_lowint1 at /Users/ash/dev/esp/esp-idf-latest-release/components/freertos/port/xtensa/xtensa_vectors.S:1105
0x401cbb9b: wifi_rf_phy_enable at ??:?
0x401cc0b2: pm_dream at ??:?
0x401cc568: pm_tbtt_process at ??:?
0x401cbacd: pm_update_next_tbtt at ??:?
0x401cbb2e: pp_timer_do_process at ??:?
0x4009a0b2: ppTask at ??:?
0x40092c6a: vPortTaskWrapper at /Users/ash/dev/esp/esp-idf-latest-release/components/freertos/port/xtensa/port.c:168
ELF file SHA256: 2e22eff32da66b1f

[zhangyanjiao]

@ ChrisAlfred ,
Please provide your commit ID on release/v4.2, thus we can figure out the specific code.

[lcrocker]

I am having exactly the same issue. The wifi task is triggering the watchdog, and every time this error is present.
I am sending MQTT packets to Google Cloud every 15 seconds.

git log of ~/esp reports:

commit 1067b28707e527f177752741e3aa08b5dc64a4d7

And here's the console output (it's about 50/50 whether the frozen task is "wifi" or "tiT").

E (2809517) wifi:ieee80211_ioctl.c 1443

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

abort() was called at PC 0x4011c1b8 on core 0

Backtrace:0x400913af:0x3ffbe910 0x40091bb5:0x3ffbe930 0x40098671:0x3ffbe950 0x4011c1b8:0x3ffbe9d0 0x40083059:0x3ffbe9f0 0x401b346b:0
x3ffd5a40 0x401b397e:0x3ffd5a60 0x4018199a:0x3ffd5a90 0x40171bb9:0x3ffd5ab0 0x40171eac:0x3ffd5ad0 0x40171ef6:0x3ffd5b10 0x40128cd0:0
x3ffd5b30 0x401aed6d:0x3ffd5b50 0x4013e41f:0x3ffd5b70 0x4013de85:0x3ffd5b90 0x40137cb2:0x3ffd5bb0 0x40137fa6:0x3ffd5bd0 0x40138f51:0
x3ffd5c00 0x40138fa5:0x3ffd5c40 0x40138fcd:0x3ffd5c70 0x40133c02:0x3ffd5ca0 0x40134891:0x3ffd5cd0 0x4013f5bc:0x3ffd5d00 0x4013ff6d:0
x3ffd5d20 0x4012c4d1:0x3ffd5d40 0x4012c578:0x3ffd5d60 0x40094d51:0x3ffd5d90

[lcrocker]

Here's a better backtrace. So it appears the function "wifi_rf_phy_enable" is to blame. Perhaps it's spin-waiting for the phy to come up and that's blocked or slowed somehow?

0x400913af: panic_abort at /home/lee/esp/esp-idf/components/esp_system/panic.c:354

0x40091bb5: esp_system_abort at /home/lee/esp/esp-idf/components/esp_system/system_api.c:112

0x40098671: abort at /home/lee/esp/esp-idf/components/newlib/abort.c:46

0x4011c434: task_wdt_isr at /home/lee/esp/esp-idf/components/esp_system/task_wdt.c:184 (discriminator 1)

0x40083059: _xt_lowint1 at /home/lee/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1105

0x401b36ef: wifi_rf_phy_enable at ??:?

0x401b3c02: pm_dream at ??:?

0x401b40b8: pm_tbtt_process at ??:?

0x401b3621: pm_update_next_tbtt at ??:?

0x401b3682: pp_timer_do_process at ??:?

0x4009a1da: ppTask at ??:?

0x40094d51: vPortTaskWrapper at /home/lee/esp/esp-idf/components/freertos/port/xtensa/port.c:168

[axellin]

Here's a better backtrace. So it appears the function "wifi_rf_phy_enable" is to blame. Perhaps it's spin-waiting for the phy to come up and that's blocked or slowed somehow?

Can you create an issue on https://github.com/espressif/esp-idf/issues/new/choose

[axellin]

Here's a better backtrace. So it appears the function "wifi_rf_phy_enable" is to blame. Perhaps it's spin-waiting for the phy to come up and that's blocked or slowed somehow?

0x400913af: panic_abort at /home/lee/esp/esp-idf/components/esp_system/panic.c:354

0x40091bb5: esp_system_abort at /home/lee/esp/esp-idf/components/esp_system/system_api.c:112

0x40098671: abort at /home/lee/esp/esp-idf/components/newlib/abort.c:46

0x4011c434: task_wdt_isr at /home/lee/esp/esp-idf/components/esp_system/task_wdt.c:184 (discriminator 1)

0x40083059: _xt_lowint1 at /home/lee/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1105

0x401b36ef: wifi_rf_phy_enable at ??:?

0x401b3c02: pm_dream at ??:?

0x401b40b8: pm_tbtt_process at ??:?

0x401b3621: pm_update_next_tbtt at ??:?

0x401b3682: pp_timer_do_process at ??:?

0x4009a1da: ppTask at ??:?

0x40094d51: vPortTaskWrapper at /home/lee/esp/esp-idf/components/freertos/port/xtensa/port.c:168

Above log is similar to https://github.com/espressif/esp-idf/issues/6744
What is your esp-idf version? (git describe --tags output)?