Unhandled interrupt 3 on cpu 0!

[pctj101]

Hello,

After leaving my ESP32 running for a while... I see this printed a few hundred times before a WDT panics the system:

Unhandled interrupt 3 on cpu 0!

Where can I read more about what commonly raises interrupt 3 (what is it?)
From what I can tell, it "doesn't really matter" since it's just a warning right? So the unhandled interrupt isn't directly responsible for a WDT panic?

Shortly after, I see the IDLE0 doesn't feed the WDT and crashes the system. I was under the impression that IDLE0 is the... base system IDLE? Isn't my app_main idle.. IDLE1? In otherwords... did the "OS" crash the system and not me?

Code: Select all

[0;31mE (t21265843) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (r21265843) task_wdt:  - IDLE0 (CPU 0)                                                                                                        
E (u21265843) task_wdt: Tasks currently running:                                                     
E (2e1265843) task_wdt: CPU 0: IDLE0                                                                                               
E ("21265843) task_wdt: CPU 1: myapp                                                                  
E (e21265843) task_wdt: Aborting.                                                                                        
abort() was called at PC 0xx400d36e7 on core 0                                                                                                                                                  
ELF file SHA256: f49213245fdba53af8eb08abb73e033d9706b8c1c2f91f8598aee4c5a71d3e9e
Backtrace: 0x4008906c:0x3ffb0b80 0x400892ed:0x3ffb0ba0 0x400d36e7:0x3ffb0bc0 0x400844fd:0x3ffb0be0 0x400d3cf7:0x3ffbf340 0x4008b01d:0x3ffbf360 0x400898a5:0x3ffbf380
0x4008906c: invoke_abort at /Users/awef/esp/esp-idf/components/esp32/panic.c:715      
0x400892ed: abort at /Users/awef/esp/esp-idf/components/esp32/panic.c:715             
0x400d36e7: task_wdt_isr at /Users/awef/esp/esp-idf/components/esp32/task_wdt.c:252
0x400844fd: _xt_lowint1 at /Users/awef/esp/esp-idf/components/freertos/xtensa_vectors.S:1154          
0x400d3cf7: esp_vApplicationIdleHook at /Users/awef/esp/esp-idf/components/esp32/freertos_hooks.c:51  
0x4008b01d: prvIdleTask at /Users/awef/esp/esp-idf/components/freertos/tasks.c:5093
0x400898a5: vPortTaskWrapper at /Users/awef/esp/esp-idf/components/freertos/port.c:403

Thanks for the help!

[ESP_Sprite]

No idea what the unhandled interrupt is about; it should definitely not be there, but without your code, there's no way to figure out why that line is printed.

The task watchdog works on the assumption that in a correctly-working system, no task uses the CPU, and if it does it does so because of a programming error. This is enforced by having the idle task feed the watchdog every now and then. In this case, your myapp seems to be hogging CPU 1, the idle task for that CPU doesn't get any time and can't feed the watchdog, and the watchdog eventually panics the system.

[pctj101]

Thanks ESP_Sprite. I'm locking some tasks to CPU1 to free up CPU0 due to the error:

[0;31mE (t21265843) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (r21265843) task_wdt: - IDLE0 (CPU 0)

Let's see how it goes.

Is there a list of interrupt #'s and their common uses so that I can start guessing what interrupt #3 is?

[WiFive]

https://github.com/espressif/esp-idf/bl ... soc.h#L359

[pctj101]

Oh no! No default for #3 hahahaha... thanks everyone!