RE: [ECOS] network problem

[John Mills <johnmills at speakeasy dot net>]

Rick -

I have just run to ground a problem with very similar symptoms. It turned
out that the 'socket' pool ("zone") was depleted by unrecoverable, stale
TCP connection records. I tracked this down by adding a counter for
allocated/ deallocated data structures from that pool and diagnostic
printouts of the count as sockets were allocated or freed. Though we
noticed the problem with web inquiries, it turned out to have other
effects - like your inability to open a 'telnet' connection.

As I understand eCos 'zones', each is initially allocated a fixed memory
block based on the size of a specific data structure and the number of
such structures they are expected to provide. Thus a simple counter will
reflect where you stand with respect to a particular pool's capacity and
you probably don't have to dig into the zone alloc/dealloc mechanism.

HTH.

 - John Mills 

DISCLAIMER: I'm a relative beginner with eCos.

On Tue, 28 Aug 2007, Rick Davis wrote:

> Andrew,
> 
> After I sent the e-mail this morning, it stopped working in another way.
> http stopped responding but pings still worked. I have a simple telnet
> server on my application and it was failing trying to bind with "Try again
> later". In_pcbbind was failing because in_pcbinshash was failing indicating
> it couldn't MALLOC memory. I turned on fancy asserts and tracing and am
> testing again. It usually take 12 Hrs or more to fail. In_pcbhash MALLOCs
> from the network pool so I am monitoring that. Any ideas why the network
> pool would run out of memory? Can it get fragmented?
> 
> Thanks,
> Rick Davis


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss