[Ovmsdev] Crash random time

[Michael Balzer]

If you only get four addresses in the backtrace, that's normally a WDT. Also in this case.

The backtrace then only is the WDT abort. Also, as the watchdog normally does not trigger on the task causing the issue, this isn't easily debuggable. We could
try to catch the WDT info that's currently only sent to USB, but even that is mostly no real hint. For example if something blocks event processing, the DukTape
watchdog will eventually trigger with…

E (139142) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (139142) task_wdt:  - OVMS DukTape (CPU 1)
E (139142) task_wdt: Tasks currently running:
E (139142) task_wdt: CPU 0: IDLE0
E (139142) task_wdt: CPU 1: IDLE1
E (139142) task_wdt: Aborting.
abort() was called at PC 0x400e709c on core 0

So adding the MyEvents.m_current_callback info to the crash debug data would make more sense.

Regards,
Michael


Am 14.04.20 um 05:51 schrieb Tamás Kovács:
> I used ovms.dexters-web.de/firmware/ota <http://ovms.dexters-web.de/firmware/ota> url to download the 3.2.011-172-g51b71688 version fw.
>
> Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> ezt írta (időpont: 2020. ápr. 14., K, 3:34):
>
>     Which firmware are you using (the URL you download from).
>
>     Best approach is to use Michael’s a2l script, give it the backtrace addresses, and the .elf file for firmware, and it will output an annotated backtrace
>     that we can see where the crash occurred.
>
>     Regards, Mark.
>
>>     On 12 Apr 2020, at 10:49 PM, Tamás Kovács <kommykt at gmail.com <mailto:kommykt at gmail.com>> wrote:
>>
>>     More info from crash. I see the following errors before crash (picture attached). Now i disable vfs logging, and run a can loggint to savyyCAN, this is
>>     the fastest mode to crash the module. i receive ~700k can messages. 
>>
>>     Tamás Kovács <kommykt at gmail.com <mailto:kommykt at gmail.com>> ezt írta (időpont: 2020. ápr. 12., V, 9:14):
>>
>>         Car Peugeot iOn used TRIO vehicle type.
>>
>>         Last crash: abort() was called on core 0 Backtrace: 0x4008b03f 0x4008b2d5 0x400e709c 0x40083d96 Version: 3.2.011-172-g51b71688/ota_1/eap (build idf
>>         v3.3-beta3-776-g3d198cd50 Apr 11 2020 11:57:14)
>>
>>         Crash at 2020.04.11 18:59 and 20:59, 04.12 09:06
>>         Created a log file the first 2 time only info level, but last with debug level. And another on OVMS SHELL is see many dropped ticker event before
>>         crash, but not show in log file.
>>
>>
>>
>>     -- 
>>     Üdvözlettel:
>>     Kovács Tamás
>>
>>     <Screenshot 2020-04-12 at 16.42.20.png>_______________________________________________
>>     OvmsDev mailing list
>>     OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>     http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>     _______________________________________________
>     OvmsDev mailing list
>     OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>     http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
>
> -- 
> Üdvözlettel:
> Kovács Tamás
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200414/313ddec8/attachment.htm>