All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Nathan Poznick <poznick@conwaycorp.net>,
	Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Sat, 1 Dec 2001 13:17:59 +0300	[thread overview]
Message-ID: <20011201131759.B11856@castle.nmd.msu.ru> (raw)
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com> <20011129095107.A17457@conwaycorp.net> <3C070FEC.3602CB49@pobox.com> <20011130114506.A4789@bee.lk> <15367.44557.930845.66428@abasin.nj.nec.com> <20011130163131.A12298@conwaycorp.net> <20011130161717.G504@mikef-linux.matchmail.com>
In-Reply-To: <20011130161717.G504@mikef-linux.matchmail.com>; from "Mike Fedyk" on Fri, Nov 30, 2001 at 04:17:17PM

Hi,

On Fri, Nov 30, 2001 at 04:17:17PM -0800, Mike Fedyk wrote:
> 
> On Fri, Nov 30, 2001 at 04:31:31PM -0600, Nathan Poznick wrote:
> > Thus spake Sven Heinicke:
> > > 
> > > I have eepro100's on other systems and never had a problem.  They
> > > never have been made to work as hard as the DELLs though.  I am
> > > trying the same DELL with a 3C996-T 1000Bt card using the driver from
> > > 3COM (we plan on moving that system to a 1000Bt system but the switch
> > > hasn't arrived yet) and it is running at 100Bt with the same
> > > software.  If you don't hear form me assume it surrived.  Been up a
> > > day so far, took the DELL like 3 days of heavy use to crash before.
> > 
> > Ok, I finally had a chance to work on this, and here's what I know:
> > 
> > 1) I found a workload under which I was able to reliably make the
> > network on the machine die (a few hundred of the "eth0: card reports
> > no resources." errors showed up which continued until I took down the
> > network and removed the module).  Unfortunately, the workload was with
> > an in-house app, so all I can describe are the conditions associated
> > with it: 2 processes with a total of about 600 threads, 1.5gb of
> > memory, about 500 network connections, and a lot of disk and network
> > I/O. 

Do you see "can't fill rx buffer" messages?
If so, then your load is too big, and memory management is incapable of
freeing memory in time.
Right now the kernel doesn't allow to increase atomic allocation
reservation (which is a serious misfeature), so you need to hack and
change the reservation in the kernel.

If the network doesn't come alive when you remove the load, it's a second
problem, a bug in the driver.  I've seen such reports, but they aren't
frequent.  On my computer, the driver resumes operations well.
Why the driver can't do it for some people needs deep investigations.

> > 
> You can run the test against eepro100 with tcpdump redirected to a log file,
> and post that on the web somewhere.  That would probably be helpful.

tcpdumps won't help.

	Andrey

  reply	other threads:[~2001-12-01 10:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 15:25 2.4.16 freezed up with eepro100 module Sven Heinicke
2001-11-29 15:51 ` Nathan Poznick
2001-11-29 16:14   ` Sven Heinicke
2001-11-30  4:49   ` J Sloan
2001-11-30  5:45     ` Anuradha Ratnaweera
2001-11-30  5:57       ` David Rees
2001-11-30  6:07         ` SBP2 Support for multiple LUNs - Changers ?? Ramaraj Pandian
2001-11-30 14:23       ` 2.4.16 freezed up with eepro100 module Nathan Poznick
2001-11-30 16:04       ` Sven Heinicke
2001-11-30 22:31         ` Nathan Poznick
2001-12-01  0:17           ` Mike Fedyk
2001-12-01 10:17             ` Andrey Savochkin [this message]
2001-12-03 15:37               ` Nathan Poznick

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=20011201131759.B11856@castle.nmd.msu.ru \
    --to=saw@saw.sw.com.sg \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=poznick@conwaycorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.