<div dir="ltr">You didn't reply to the entire list so I am adding it back.<div><br></div><div>You are using the legacy stack (cpukit/libnetworking) which is 20+ years old and IPV4 only.</div><div><br></div><div>There could be a packet which the older stack doesn't like the format of. Perhaps a number pushes something out of range. </div><div><br></div><div>Any possibility there is IPV6 on the network? I don't know how this stack reacts to that.</div><div><br></div><div>Another simple thing to try is increasing the size of the stacks and turning on the stack checker.</div><div><br></div><div>--joel</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 8, 2020 at 10:39 AM <<a href="mailto:Richard.Glossop@l3harris.com">Richard.Glossop@l3harris.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-4768697536693007704WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hi Joel,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">We are using Gaisler’s rc7 release for RTEMS 5.1. I don’t see libbsd in the map file at all, but not really sure how to tell.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">We do have an FPU and our tasks are all FP enabled. Not sure on the network stack.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> users <<a href="mailto:users-bounces@rtems.org" target="_blank">users-bounces@rtems.org</a>>
<b>On Behalf Of </b>Joel Sherrill<br>
<b>Sent:</b> Thursday, October 8, 2020 11:29 AM<br>
<b>To:</b> Thomas Doerfler <<a href="mailto:Thomas.Doerfler@imd-systems.de" target="_blank">Thomas.Doerfler@imd-systems.de</a>><br>
<b>Cc:</b> <a href="mailto:rtems-users@rtems.org" target="_blank">rtems-users@rtems.org</a> <<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: RTEMS Network Stack and Managed Switch<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Oct 8, 2020 at 10:25 AM Thomas Doerfler <<a href="mailto:Thomas.Doerfler@imd-systems.de" target="_blank">Thomas.Doerfler@imd-systems.de</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Richard,<br>
<br>
what hardware/BSP are you running on?<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thomas beat me on this. :)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Also the RTEMS version and network stack (legacy vs libbsd). <u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
Just a shot in the dark: It seems the system crashes in arplookup -> ...<br>
-> svfprintf. Can it be that some networking routine tries to print a<br>
message with floating point, but the FPU is disabled for the<br>
corresponding task?<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Since I recall you are using a LEON, this is indeed a very likely culprit.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The stack trace is a bit odd since nothing in libc would call _Internal_XXX.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">--joel <u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
wkr,<br>
<br>
Thomas.<br>
<br>
Am 08.10.20 um 17:15 schrieb <a href="mailto:Richard.Glossop@L3Harris.com" target="_blank">Richard.Glossop@L3Harris.com</a>:<br>
> We have discovered a problem with the RTEMS network stack reaching the<br>
> RTEMS _Terminate function when the interfaces are attached to a managed<br>
> switch (in this case a Cisco 3560).<br>
> <br>
> <br>
> <br>
> This does not occur with direct connections or when attached to a layer<br>
> 2 unmanaged switch (NetGear or SMC). Of course the 3560 puts out a lot<br>
> of traffic that a layer 2 switch does not (spanning tree, CDP etc….)<br>
> <br>
> <br>
> <br>
> So it seems the managed switch is putting out traffic that is bringing<br>
> RTEMS down.<br>
> <br>
> <br>
> <br>
> Has anyone seen this behavior? Have you determined the root cause?<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> I set a break point and caught the following backtrace:<br>
> <br>
> <br>
> <br>
> #0 0x6006ec90 0x60200180 <_Terminate+0x4><br>
> <br>
> #1 0x6006ece0 0x602001e8 <_Internal_error+0x8><br>
> <br>
> #2 0x600da250 0x60200248 <_svfprintf_r+0x14><br>
> <br>
> #3 0x600d5810 0x60200420 <snprintf+0x58><br>
> <br>
> #4 0x60073bac 0x60200508 <inet_ntop4+0x24><br>
> <br>
> #5 0x60073e70 0x60200580 <inet_ntop+0x280><br>
> <br>
> #6 0x60073b78 0x60200630 <inet_ntoa_r+0x1c><br>
> <br>
> #7 0x60076340 0x60200698 <arplookup+0x78><br>
> <br>
> #8 0x60076e34 0x60200710 <arpintr+0x20c><br>
> <br>
> #9 0x6008861c 0x602007c0 <networkDaemon+0xa0><br>
> <br>
> #10 0x60088164 0x60200828 <taskEntry+0x20><br>
> <br>
> #11 0x6006d210 0x60200888 <_Thread_Entry_adaptor_numeric+0x8><br>
> <br>
> #12 0x6006c464 0x602008e8 <_Thread_Handler+0x60><br>
> <br>
> #13 0x6006c404 0x60200948 <_Thread_Handler+0><br>
> <br>
> <br>
> <br>
> <br>
> <br>
> CONFIDENTIALITY NOTICE: This email and any attachments are for the sole<br>
> use of the intended recipient and may contain material that is<br>
> proprietary, confidential, privileged or otherwise legally protected or<br>
> restricted under applicable government laws. Any review, disclosure,<br>
> distributing or other use without expressed permission of the sender is<br>
> strictly prohibited. If you are not the intended recipient, please<br>
> contact the sender and delete all copies without reading, printing, or<br>
> saving.<br>
> <br>
> <br>
> _______________________________________________<br>
> users mailing list<br>
> <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
> <br>
<br>
-- <br>
IMD Ingenieurbuero fuer Microcomputertechnik<br>
Thomas Doerfler Herbststrasse 8<br>
D-82178 Puchheim Germany<br>
email: <a href="mailto:Thomas.Doerfler@imd-systems.de" target="_blank">Thomas.Doerfler@imd-systems.de</a><br>
PGP public key available on request<br>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
<span><span><br> </span> </span><br>
<div><span style="font-family:"Times New Roman""><span style="font-size:14px">CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.</span></span>
<div style="font-size:14px;font-family:"Times New Roman""><br></div></div></div>
</blockquote></div>