From: John Mills <johnmills@speakeasy.net>
To: eCos Users <ecos-discuss@ecos.sourceware.org>
Cc: Rick Davis <rickdavisjr@comcast.net>
Subject: RE: [ECOS] network problem
Date: Tue, 28 Aug 2007 18:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0708281338370.13330-100000@otter.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0708281248260.12499-100000@otter.localdomain>
Rick -
You could try drastically reducing the capacity of the pool you think
you're depleting. That way you might generate the lockup in a few minutes
or an hour, instead of 12 hours.
- John Mills
On Tue, 28 Aug 2007, John Mills wrote:
> 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
>
>
--
- John Mills
john.m.mills@alum.mit.edu
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-08-28 18:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 6:48 Rick Davis
2007-08-27 8:12 ` Andrew Lunn
2007-08-28 9:00 ` Rick Davis
2007-08-28 16:09 ` Andrew Lunn
2007-08-28 16:29 ` Rick Davis
2007-08-28 18:10 ` John Mills
2007-08-28 18:42 ` John Mills [this message]
2007-08-28 18:42 ` Rick Davis
2007-08-29 19:12 ` John Mills
2007-09-01 10:38 ` Andrew Lunn
2007-09-01 12:05 ` Rick Davis
2007-09-01 12:32 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2007-08-30 23:09 Rick Davis
2005-05-14 19:55 [ECOS] : Network problem vamshi
2005-05-16 5:13 ` Gary Thomas
2002-01-11 8:30 [ECOS] network problem Andrea Acquaviva
2002-01-11 8:40 ` Andrew Lunn
2002-01-11 9:04 ` Andrea Acquaviva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0708281338370.13330-100000@otter.localdomain \
--to=johnmills@speakeasy.net \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john.m.mills@alum.mit.edu \
--cc=rickdavisjr@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).