public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Poznick <poznick@conwaycorp.net>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Mon, 3 Dec 2001 09:37:19 -0600	[thread overview]
Message-ID: <20011203153719.GA10261@conwaycorp.net> (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> <20011201131759.B11856@castle.nmd.msu.ru>
In-Reply-To: <20011201131759.B11856@castle.nmd.msu.ru>

Thus spake Andrey Savochkin:

> 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.

Yes, I saw a combination of the "can't fill rx buffer" messages and
"card reports no resources" messages, and after a while it went to
just a whole bunch (few hundred) of the "card reports no resources"
messages, which continued to scroll across the console at the rate of
one every second or so until I took down networking and removed the
eepro100 module.

> 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.

After I removed the load, I gave it about 10 minutes or so to see if
it would pick back up, but it didn't.

-- 
Nathan Poznick <poznick@conwaycorp.net>
PGP Key: http://drunkmonkey.org/pgpkey.txt

"I think everyone ought to come in and have a hot cup of cocoa and
come inside and be nice and snuggly."
-Crow (as Dr. Herly). #201

      reply	other threads:[~2001-12-04  1:45 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
2001-12-03 15:37               ` Nathan Poznick [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=20011203153719.GA10261@conwaycorp.net \
    --to=poznick@conwaycorp.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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