Re: [lwip-users] TCP break down with concurrent client accept

2018-09-07 Thread Oldrich Kepka
Hi again, I found that the reason for tcp networking to break is that there are no available semaphores to initialize. We run out of semaphores, because some connection don't close. They don't close because they are stuck in read function. while(1) { n = read(s, ...) if(n<=0) break; } close(

Re: [lwip-users] TCP break down with concurrent client accept

2018-09-04 Thread Oldrich Kepka
Hi Simon, I return to this old post. As you requested, I migrated our system to 2.0.2 using Xilinx port of LWIP. https://github.com/Xilinx/embeddedsw/tree/master/ThirdParty/sw_services/lwip202 and I observe the same behaviour that I reported above. I am able to reproduce the break with SOCKETS_D

Re: [lwip-users] TCP break down with concurrent client accept

2018-04-01 Thread goldsi...@gmx.de
On 01.04.2018 01:26, Oldrich Kepka wrote: we run lwip-1.4.0 on PPC440 and experience rare random hanging of TCP Two things that I think are worth noting: a) 1.4.0 is really old. There have been numerous fixes since that. Can you reproduce the issue with current git master? b) 1.4.0 does not co

[lwip-users] TCP break down with concurrent client accept

2018-04-01 Thread Oldrich Kepka
Hi, we run lwip-1.4.0 on PPC440 and experience rare random hanging of TCP. I was able to create a minimal working example to reproduce the hang: Setup a tcp server on the PPC: int socketId = socket(AF_INET, SOCK_STREAM, 0); if(socketId == -1){...return;} struct sockaddr_in server;