archive mirror
 help / color / mirror / Atom feed
From: David Ford <>
To: Michal Margula <>
Subject: Re: Disaster under heavy network load on 2.4.x
Date: Tue, 12 Jun 2001 11:18:48 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

It looks like you don't have 'lo' configured, i.e. your interface.


Michal Margula wrote:

>My friend told me to noticed you about problems I had with 2.4.x line of
>kernels. I started up from 2.4.3. Under heavy load I was getting
>messages from telnet, ping, nmap "No buffer space available". Strace
>told me it was error marked as ENOBUFS.
>First thought was it was my fault. I asked many people and nobody could
>help me. So I tried 2.4.5. It was a disaster also (should I mention few
>Second thought was to try 2.2.19 and it was good choice. Now there are
>almost no messags like those above. Only thing that still happens is
>"Neihgbour table overflow".
>Some data about my Linux box:
>2 x PIII 800 MHz/1024 MB; 2 x Intel EExpres 100; 3 x 3com 3c900B-Combo.
>Summarizing all traffic about 5mbit at the moment.
># arp -an | wc -l
>   1018
>Any more info needed?
>PS. It would be nice to be CCed with replies, beacause I am not
>subscribed to LKML.

  parent reply	other threads:[~2001-06-12 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 20:03 Michal Margula
2001-06-11 21:02 ` Martin Josefsson
2001-06-12 18:18 ` David Ford [this message]
     [not found] <>
2001-06-13  9:01 ` Andi Kleen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Disaster under heavy network load on 2.4.x' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 NNTP newsgroup(s).