[En-Nut-Discussion] TCP stops working after some time

[Harald Kipp]

Roman,

Right, it's really difficult to track down such problems.
Beside that, most of the failures we found are in the
application code (or even hardware failures sometimes).
Thus, it is most important to reduce the test case to a
bare minimum.

We started with a simple TCP server first, which runs
stable for more than a week. Next we added receive timeout.
Now the error appeared after about three days. We will
add several threads and try to trigger the failure
more often. Otherwise it will become too difficult to
test future modifications.

I noted with interest, that your app is running without TCP.
But without a simple test case the problem can be located
anywhere.

Harald

At 12:30 20.12.2004 +0300, you wrote:
>Hello,
>
>We have approximately one hang per week or two. The board does not
>have Ethernet and TCP, only threads, LCD and USART. I tried CVS
>version but it hangs too. Now I am finding a way to hang the board a bit
>often, it is very hard to debug and analyze such rare failures.
>
>Monday, December 20, 2004, 12:07:14 PM, you wrote:
>
> > Long time ago since this had been reported. Last night
> > our long time test failed. Ethernut seems to be dead.
> > Despite similar situations reported by someone else,
> > there was even no ping response.
>
>--
>Best regards,
>  Roman