search

openvehicles / Open-Vehicle-Monitoring-System-3

Open Vehicle Monitoring System - Version 3
http:///www.openvehicles.com/
Other
589 stars 225 forks source link

FYI: crash in eap version 3.3.003-190-ge19f95c4/ota_0/eap #792

Open jollyjinx opened 1 year ago

jollyjinx commented 1 year ago

Trying to keep the module at 6V on OBD asleep (which it fails) I just saw:

Last boot was 10 second(s) ago Time at boot: 2022-12-05 17:44:00 CET This is reset #1 since last power cycle Detected boot reason: EarlyCrash (12/12) Reset reason: Exception/panic (4) Crash counters: 1 total, 1 early
Last crash: abort() was called on core 0 Current task on core 0: wifi, 864 stack bytes free Current task on core 1: OVMS Console, 4032 stack bytes free

Backtrace: 0x4008ddca 0x4008e065 0x40092517 0x400928cf 0x40092f05 0x400843a8 0x40084446 0x40087245 0x40098a0d 0x4009a7b9 0x400976fe Version: 3.3.003-190-ge19f95c4/ota_0/eap (build idf v3.3.4-849-g6e214dc335 Nov 30 2022 23:08:18)

Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600 Firmware: 3.3.003-190-ge19f95c4/ota_0/eap (build idf v3.3.4-849-g6e214dc335 Nov 30 2022 23:08:18) Running partition: ota_0 Boot partition: ota_0 Factory image: 3.3.003-159-g4084027e-dirty OTA_O image: 3.3.003-190-ge19f95c4 OTA_1 image: 3.3.003-122-g0e0946a3

after the module went to sleep and woke up again ( even though still at 6V) it tells me that it reset and not woke from sleep.

Last boot was 102 second(s) ago Time at boot: 2022-12-05 17:51:06 CET This is reset #0 since last power cycle Detected boot reason: PowerOn (1/14) Reset reason: Unknown/unset (0) Crash counters: 0 total, 0 early Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600 Firmware: 3.3.003-190-ge19f95c4/ota_0/eap (build idf v3.3.4-849-g6e214dc335 Nov 30 2022 23:08:18) Running partition: ota_0 Boot partition: ota_0 Factory image: 3.3.003-159-g4084027e-dirty OTA_O image: 3.3.003-190-ge19f95c4 OTA_1 image: 3.3.003-122-g0e0946a3 RebootClear counters

dexterbg commented 1 year ago

Use the included a2ll script to decode backtraces. The .elf file is on the server aside the .bin (see e.g. https://ovms.dexters-web.de/firmware/ota/v3.3/edge/).

In this case, the backtrace shows the esp-idf memory management somehow got corrupted, as it found a block that should have been free but wasn't. So a very rare fault. That may be due to some rare out of band write, hardly trackable or fixable.