[Ovmsdev] can log vfs crashes
Derek Caudwell
d.caudwell at gmail.com
Wed Sep 30 14:43:42 HKT 2020
Hi Michael,
When the vehicle is not set to poll and only receiving can1 messages I
managed to obtain a 10Mb file - logging a variety of signals some with 10ms
timing without any issues. However, when polling and can1/can2 are
operating and I try to log the same signals I get the following crash
trace. I would suspect the underlying cause of the crashing relates to both
buses being active as opposed to the polling but that may not be the case.
Last crash: abort() was called on core 0 Backtrace: 0x4008e627 0x4008e8c1
0x400e7060 0x40083f6a Event: ticker.1 at esp32wifi 0 secs WDT tasks:
IDLE1|OVMS DukTape
0x4008e627 is in invoke_abort
(/mnt/c/linux/ovms/esp-idf/components/esp32/panic.c:156).
151 #endif
152 while (1) {
153 if (esp_cpu_in_ocd_debug_mode()) {
154 __asm__ ("break 0,0");
155 }
156 *((int *) 0) = 0;
157 }
158 }
159
160 void abort()
0x4008e8c1 is in abort
(/mnt/c/linux/ovms/esp-idf/components/esp32/panic.c:171).
166 * don't overwrite that.
167 */
168 if (esp_reset_reason_get_hint() == ESP_RST_UNKNOWN) {
169 esp_reset_reason_set_hint(ESP_RST_PANIC);
170 }
171 invoke_abort();
172 }
173
174
175 static const char *edesc[] = {
0x400e7060 is in task_wdt_isr
(/mnt/c/linux/ovms/esp-idf/components/esp32/task_wdt.c:174).
169 esp_task_wdt_isr_user_handler();
170 if (twdt_config->panic){ //Trigger Panic if configured to
do so
171 ESP_EARLY_LOGE(TAG, "Aborting.");
172 portEXIT_CRITICAL_ISR(&twdt_spinlock);
173 esp_reset_reason_set_hint(ESP_RST_TASK_WDT);
174 abort();
175 }
176
177 portEXIT_CRITICAL_ISR(&twdt_spinlock);
178 }
0x40083f6a is at
/mnt/c/linux/ovms/esp-idf/components/freertos/xtensa_vectors.S:1154.
1149 wsr a0, PS
1150 rsync
1151
1152 /* OK to call C code at this point, dispatch user ISRs */
1153
1154 dispatch_c_isr 1 XCHAL_INTLEVEL1_MASK
1155
1156 /* Done handling interrupts, transfer control to OS */
1157 call0 XT_RTOS_INT_EXIT /* does not return
directly here */
1158
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200930/3d8c241c/attachment-0002.htm>
More information about the OvmsDev
mailing list