public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Colin Ford <colin.ford@pipinghotnetworks.com>
Cc: Ecos Mailing List <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Out of MBUF panic
Date: Mon, 11 Dec 2000 10:29:00 -0000	[thread overview]
Message-ID: <20001211123234.A3190@visi.com> (raw)
In-Reply-To: <3A350AB5.EA369378@pipinghotnetworks.com>

On Mon, Dec 11, 2000 at 05:11:17PM +0000, Colin Ford wrote:

> > I'm testing an eCos system using the GoAhead web server, and
> > after fetching 5 or 6 modes pages, I always get an "out of
> > mbuf" panic.  This is with eCos 1.3.1 and net 1.0b1 (with some
> > patches to fix mbuf corruption race conditions), with default
> > settings for everything.
>
> I'm using the GoAhead web server on a MIPS R3000 with the
> latest CVS version of eCos and net. I had a problem with memory
> getting corrupted because of a select in the function
> socketSelect in the file sockGen.c
> 
> Basically the memory for the file descriptors was way to small
> so I made sure it was the size of the fd_set (32). Now it works
> a treat.

I'm assuming you did something like this at the beginning of
socketSelect:

    readFds = balloc(B_L, sizeof(fd_set));
	memset(readFds, 0,  sizeof(fd_set));
	writeFds = balloc(B_L,  sizeof(fd_set));
	memset(writeFds, 0,  sizeof(fd_set));
	exceptFds = balloc(B_L,  sizeof(fd_set));
	memset(exceptFds, 0,  sizeof(fd_set));

That fix improved things a bit.  Now I can fetch the page about
30 times before I get an out of MBUFs panic.

I'm still trying to build with current CVS, but the Ethernet
driver architecture has changed, and that's going to take some
work to get running.  :(

-- 
Grant Edwards
grante@visi.com

      reply	other threads:[~2000-12-11 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-11  8:53 Grant Edwards
2000-12-11  9:11 ` Colin Ford
2000-12-11 10:29   ` Grant Edwards [this message]

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=20001211123234.A3190@visi.com \
    --to=grante@visi.com \
    --cc=colin.ford@pipinghotnetworks.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).