<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi,<br>
<br>
That's exactly what I've figured out pulling an all-nighter. If I
set the IPv4-ACL "Deny UDP src=192.168.254.228:5353 dst=any" (.228
is the OVMS) on the switch for the port my AP hits the network
everything works stable.<br>
<br>
My Vehicle-ID on the Vehicle configuration page is "OVMS". So
nothing weird at all...<br>
<br>
Is there a way to disable mDNS via the shell (I dont need it
anyhow)? With you suggesting doing a new build though I guess no?<br>
<br>
Thanks, Soko<br>
<br>
@Michael: thx for the tip<br>
<br>
<div class="moz-cite-prefix">On 05.07.2023 01:39, Mark Webb-Johnson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3614EC01-B3E5-46B8-83BD-F7DDF88A17D7@webb-johnson.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Not sure how reliable that short backtrack is, but here is what it
shows:
<div><br>
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;">
<div>
<div>$ ../a2l ovms3.elf 0x4028128f 0x402823bf</div>
<div>Using elf file: ovms3.elf</div>
<div>0x4028128f is in mdns_parse_packet
(C:/Users/soko/Source/OVMS/home/soko/esp-idf/components/mdns/mdns.c:2839).</div>
<div>0x402823bf is in _mdns_service_task
(C:/Users/soko/Source/OVMS/home/soko/esp-idf/components/mdns/mdns.c:3545).</div>
<div>3540<span class="Apple-tab-span" style="white-space:pre"> </span>in
C:/Users/soko/Source/OVMS/home/soko/esp-idf/components/mdns/mdns.c</div>
</div>
</blockquote>
<div>
<div><br>
</div>
<div>So that implies a crash parsing a MDNS packet.</div>
<div><br>
</div>
<div>If that is repeatable, it would be a bug in the ESP IDF for
mdns. You could try disabling CONFIG_OVMS_COMP_MDNS in your
build and see if that works around the issue. There is
also CONFIG_MDNS_TASK_STACK_SIZE and CONFIG_MDNS_MAX_SERVICES
which may be related. But that is based on the single
backtrace, which may be wrong.</div>
<div><br>
</div>
<div>The only other thing I can think of is the MDNS service
packets we transmit. What is your vehicle ID? Anything unusual
(non-ascii characters, long length, etc)?</div>
<div><br>
</div>
<div>Regards, Mark</div>
<div><br>
<blockquote type="cite">
<div>On 4 Jul 2023, at 6:10 PM, Soko <a class="moz-txt-link-rfc2396E" href="mailto:ovms@soko.cc"><ovms@soko.cc></a>
wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div> Hi Mark,<br>
<br>
I have the exact bin & elf I'm using (I've compiled
it myself back in the day...). I've also found the
script you are mentioning, but it seems to be a linux
script, I'm on windows.<br>
Looking at the script though - educated guessing - it
just looks at the address in the ELF file.<br>
Opening the ELF file with an hex-editor in windows
reveals it ends at 0x0240D5DB.<br>
<br>
<span id="cid:part1.4oiLDdZO.2ti0kr7x@soko.cc"><vwPxeAnwFzenPgJR.png></span><br>
<br>
Do I have to translate the address somehow? Or is the
a2l script doing more than just looking.<br>
<br>
I've also uploaded the bin & elf (<a
class="moz-txt-link-freetext"
href="http://soko.yourweb.de/ovms3.zip"
moz-do-not-send="true">http://soko.yourweb.de/ovms3.zip</a>)
if you wonna have a quick look.<br>
<br>
The backtrace (0x4028128f 0x402823bf) is more or less
the only constant numbers I get with each crash. So if
they are too short can I add/activate some trace which
leads to more info without connecting to a laptop (my
old devenv doesn't seem to work anymore, and it was
Windows anyhow...)<br>
<br>
thx<br>
Soko<br>
<br>
<br>
<div class="moz-cite-prefix">On 04.07.2023 03:01, Mark
Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4EDE1515-0AB4-444D-928D-831137DC6BFA@webb-johnson.net">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
To understand what is going on, you’ll need to get the
ELF file for the *exact* build of firmware you are
using, and then use the support/a2l script to decode
the backtrace addresses to something human readable.
If you can’t do this, you could try by letting us know
the firmware version you are running, where you got it
from (API or Dexters), and provide the backtrace
addresses. <span style="caret-color: rgb(0, 0, 0);">If
you are using standard firmware builds, you can
normally find the .elf file by simply change
ovms3.bin to ovms3.elf in the download URL.</span>
<div><font><span style="caret-color: rgb(0, 0, 0);"><br>
</span></font>
<div>Alternatively, connect the module over USB to a
laptop/workstation running the development build
environment and GDB stub running to capture the
panic.</div>
<div><br>
</div>
<div>The backtrace you show below (0x4028128f
0x402823bf) does not seem to be valid (too short),
and probably won’t help much.</div>
<div><br>
</div>
<div>Regards, Mark.<br>
<div><br>
<blockquote type="cite">
<div>On 4 Jul 2023, at 5:41 AM, Soko <a
class="moz-txt-link-rfc2396E"
href="mailto:ovms@soko.cc"
moz-do-not-send="true"><ovms@soko.cc></a>
wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div> Hi guys,<br>
<br>
Running happily my OVMS on my VW e-Up
since 2020 it drives my crazy since today
:(<br>
<br>
It restarts roughly every minute with this
status afterwards:<br>
------------<br>
Last boot was 28 second(s) ago<br>
Time at boot: 2023-07-03 21:25:07 CEST<br>
This is reset #1 since last power cycle<br>
Detected boot reason: Crash (12/12)<br>
Reset reason: Exception/panic (4)<br>
Crash counters: 1 total, 0 early<br>
<br>
Last crash: LoadProhibited exception on
core 0<br>
Registers:<br>
PC : 0x4028128f PS : 0x00060d30 A0 :
0x802823c2 A1 : 0x3ffe71d0<br>
A2 : 0x3ffe9f9c A3 : 0x00000000 A4 :
0x00000000 A5 : 0x00000001<br>
A6 : 0x3ffe9fe8 A7 : 0x3ffe71d0 A8 :
0x0000005b A9 : 0xffffffff<br>
A10 : 0x00000e10 A11 : 0x0000000e A12 :
0x00000010 A13 : 0x3ffbd3ac<br>
A14 : 0x3f84e83c A15 : 0x3ffbd46b SAR :
0x00000010 EXCCAUSE: 0x0000001c<br>
EXCVADDR: 0x00000004 LBEG : 0x4008b0e9
LEND : 0x4008b11d LCOUNT : 0x00000000<br>
Backtrace:<br>
0x4028128f 0x402823bf<br>
------------<br>
<br>
And now the crazy part: It only happens
when I'm connected to a specific
WiFi/network?!?!<br>
<br>
What I've tried so far:<br>
<ol>
<li>Factory Reset (multiple times)</li>
<li>Set a static IP address</li>
<li>Reconnect all cables and make sure
all are snug and tight</li>
<li>Brought OVMS closer to the AP (only
one, no mesh)<br>
</li>
<li>Restarted AP</li>
<li>Restarted DNS & DHCP Server</li>
<li>It even happens when I have no
vehicle selected after a factory reset<br>
</li>
</ol>
<p>It gets more crazy: My WiFi is via
Unifi/Ubiquity. So I can have multiple
SSIDs with the same AP. So all hardware
involved is the same...</p>
<p>When I connect to SSID "E3200", which
is network 192.168.254.0/24, the
exception happens every minute or so.<br>
When I connect to SSID "SurfHere" which
is network 192.168.179.0/24, everything
works fine!</p>
<p>Do you guys have any idea why this is
happening?<br>
</p>
I've tried to look at logs via Shell and
"log level verbose" but nothing shows up.
Is there more I can activate to log this
issue?<br>
<br>
Maybe my hardware is faulty... Where do I
get a new OVMS here in Europe/EU/Austria?
Do I have to import in from the UK (<a
class="moz-txt-link-freetext"
href="https://shop.openenergymonitor.com/ovms/"
moz-do-not-send="true">https://shop.openenergymonitor.com/ovms/</a>)?<br>
<br>
thanks heaps in advance,<br>
Soko<br>
</div>
_______________________________________________<br>
OvmsDev mailing list<br>
<a class="moz-txt-link-abbreviated
moz-txt-link-freetext"
href="mailto:OvmsDev@lists.openvehicles.com"
moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br>
<a class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
OvmsDev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></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>
</body>
</html>