From: Andrey Savochkin <saw@saw.sw.com.sg>
To: angelcode <angelcode@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18: weird eepro100 msgs
Date: Mon, 26 Feb 2001 18:09:27 -0800 [thread overview]
Message-ID: <20010226180927.A32604@saw.sw.com.sg> (raw)
In-Reply-To: <983085249.280angelcode@myrealbox.com>
In-Reply-To: <983085249.280angelcode@myrealbox.com>; from "angelcode" on Sun, Feb 25, 2001 at 07:14:09AM
On Sun, Feb 25, 2001 at 07:14:09AM +0000, angelcode wrote:
> I've been seeing the same kind of messages with an eepro100
> but they don't happen when the module is loaded. They
> happen after it has been running for a few days. I am
> running 2.4.1. I haven't seen any real problems but these
> messages still scare me.
If your network isn't stuck, it's not a real problem.
The card just reports that it feels shortage of receive buffers.
It may be real or illusional one, it's not a really big problem.
Best regards
Andrey
> > > > On Fri, 2 Feb 2001 15:01:05 -0800 (PST), Ivan Passos
> <lists@cyclades.com> wrote:
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > eth0: card reports no resources.
> > > > > eth0: card reports no RX buffers.
> > > > > (...)
next prev parent reply other threads:[~2001-02-27 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 7:14 angelcode
2001-02-27 2:09 ` Andrey Savochkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 23:01 Ivan Passos
2001-02-02 23:35 ` Ion Badulescu
2001-02-03 1:20 ` Ivan Passos
2001-02-24 1:53 ` Ivan Passos
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=20010226180927.A32604@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=angelcode@myrealbox.com \
--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
all inboxes | Powered by JetHome®