[En-Nut-Discussion] No Long Term Stability in Some Networks

[Alexander Baranov]

Hi Harald and All
I can also report that in my application using Ethernut 2.1 and Nut/OS 
versions 4.0.1 - 4.03 in the case of interrupted network connection (e.g. 
disconnected cable) the device attempting to make NutTcpConnect may hang up 
so toughly that even my external watcdog does not always help.
Alexander

----- Original Message ----- 
From: "Harald Kipp" <harald.kipp at egnite.de>
To: <en-nut-discussion at egnite.de>
Sent: Monday, April 24, 2006 9:40 AM
Subject: [En-Nut-Discussion] No Long Term Stability in Some Networks


> Hi all,
>
> One customer, who created a product based on the Ethernut 1.3
> design, reported, that the TCP stack stops running in specific
> networks. While it runs reliably in other LANs.
>
> He is using Nut/OS 3.9.7.1.
>
> This corresponds to a few similar reports in this list. It may
> be interesting to note, that the OS kernel continues to run.
> The problem is obviously related to the Ethernet receiver,
> probably due to broadcast overflows. But the latter is still an
> assumption.
>
> I'd like to add, that Ethernut 3 (ARM) passed several heavy load
> tests recently. This may point to a failure in the Ethernet drivers,
> which are still platform specific.
>
> Harald
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>