From: Andrew Morton <akpm@zip.com.au>
To: Teodor Iacob <Teodor.Iacob@astral.kappa.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eth0: memory shortage
Date: Wed, 03 Jul 2002 13:25:13 -0700 [thread overview]
Message-ID: <3D235DA9.2B3D0E4@zip.com.au> (raw)
In-Reply-To: 20020703190931.GA13103@linux.kappa.ro
Teodor Iacob wrote:
>
> Hello,
>
> I keep getting these messages (like about twice a day) in the messages:
> eth0: memory shortage
> eth0: memory shortage
> eth1: memory shortage
> eth1: memory shortage
>
> Any idea what could be the reason behind this?
>
It means that the ethernet driver's Rx interrupt handler was not
able to allocate a new receive buffer - there wasn't enough memory
available.
The `kswapd' kernel thread is supposed to make memory available
for interrupt context but in this case it is obviously not keeping
up.
The driver recovers from the failed allocation, so things are OK.
-
prev parent reply other threads:[~2002-07-03 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 19:09 eth0: memory shortage Teodor Iacob
2002-07-03 20:15 ` Mitch Adair
2002-07-03 20:25 ` Andrew Morton [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=3D235DA9.2B3D0E4@zip.com.au \
--to=akpm@zip.com.au \
--cc=Teodor.Iacob@astral.kappa.ro \
--cc=linux-kernel@vger.kernel.org \
/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