<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
If you only get four addresses in the backtrace, that's normally a
WDT. Also in this case.<br>
<br>
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…<br>
<tt><br>
</tt><tt>E (139142) task_wdt: Task watchdog got triggered. The
following tasks did not reset the watchdog in time:</tt><tt><br>
</tt><tt>E (139142) task_wdt: - OVMS DukTape (CPU 1)</tt><tt><br>
</tt><tt>E (139142) task_wdt: Tasks currently running:</tt><tt><br>
</tt><tt>E (139142) task_wdt: CPU 0: IDLE0</tt><tt><br>
</tt><tt>E (139142) task_wdt: CPU 1: IDLE1</tt><tt><br>
</tt><tt>E (139142) task_wdt: Aborting.</tt><tt><br>
</tt><tt>abort() was called at PC 0x400e709c on core 0</tt><br>
<br>
So adding the MyEvents.m_current_callback info to the crash debug
data would make more sense.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 14.04.20 um 05:51 schrieb Tamás
Kovács:<br>
</div>
<blockquote type="cite"
cite="mid:CAGpaXUs3misoMSDOMAeKkjEgB3x96DNpYRx+oXO4+YeUbYOh6g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>I used <a
href="http://ovms.dexters-web.de/firmware/ota"
moz-do-not-send="true">ovms.dexters-web.de/firmware/ota</a>
url to download the <span style="color:rgb(0,34,0);font-family:Monaco,Menlo,Consolas,"QuickType Mono","Lucida Console","Roboto Mono","Ubuntu Mono","DejaVu Sans Mono","Droid Sans Mono",monospace;font-size:13px;white-space:pre-line">3.2.011-172-g51b71688</span> version
fw.</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Mark Webb-Johnson <<a
href="mailto:mark@webb-johnson.net" moz-do-not-send="true">mark@webb-johnson.net</a>>
ezt írta (időpont: 2020. ápr. 14., K, 3:34):<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div style="word-wrap:break-word;line-break:after-white-space">Which
firmware are you using (the URL you download from).
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards, Mark.<br>
<div><br>
<blockquote type="cite">
<div>On 12 Apr 2020, at 10:49 PM, Tamás Kovács <<a
href="mailto:kommykt@gmail.com" target="_blank"
moz-do-not-send="true">kommykt@gmail.com</a>>
wrote:</div>
<br>
<div>
<div dir="ltr">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. </div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Tamás Kovács
<<a href="mailto:kommykt@gmail.com"
target="_blank" moz-do-not-send="true">kommykt@gmail.com</a>>
ezt írta (időpont: 2020. ápr. 12., V, 9:14):<br>
</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Car Peugeot iOn used TRIO vehicle
type.</div>
<div><br>
</div>
<div><span style="color:rgb(0,34,0);font-family:Monaco,Menlo,Consolas,"QuickType Mono","Lucida Console","Roboto Mono","Ubuntu Mono","DejaVu Sans Mono","Droid Sans Mono",monospace;font-size:13px;white-space:pre-line">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)</span><br>
</div>
<div><br>
</div>
<div>Crash at 2020.04.11 18:59 and 20:59,
04.12 09:06<br>
</div>
<div>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.</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Üdvözlettel:<br>
Kovács Tamás<br>
<br>
</div>
<span
id="gmail-m_8971353022384656620cid:f_k8x5zfdu0"><Screenshot
2020-04-12 at 16.42.20.png></span>_______________________________________________<br>
OvmsDev mailing list<br>
<a href="mailto:OvmsDev@lists.openvehicles.com"
target="_blank" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br>
<a
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
target="_blank" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
OvmsDev mailing list<br>
<a href="mailto:OvmsDev@lists.openvehicles.com"
target="_blank" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br>
<a
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">Üdvözlettel:<br>
Kovács Tamás<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>