[eepro100] Re: Addressing "eth0: card reports no resources."
Andrey Savochkin
saw@saw.sw.com.sg
Mon, 22 Jan 2001 12:59:42 +0800
Hello,
On Thu, Jan 18, 2001 at 10:39:56PM +0200, Louis Mandelstam wrote:
> On Thu, 18 Jan 2001, Andrey Savochkin wrote:
> > There are two different problems related to "card reports no resources"
> > messages.
> >
> > The first one is the shortage of memory.
> > In this case this message is accompanied by "can't fill rx buffer" one, and
> > adjusting /proc/sys/vm/freepages solves the shortage.
> >
> > The second problem is "card reports no resources" reports starting right
> > after driver initialization.
> > It happens because of a hardware bug, for which Donald Becker recently found
> > a workaround and implemented it in his driver available from ftp://scyld.com.
> > The driver shipped with mainstream Linux kernels will have the same fix soon.
>
> Well, we don't have either of the above two scenarios.
>
> We get "card reports no resources" all the time, with the frequency
> apparently related to load (or rather, we see them more frequently during
> our peak times). We do not see anything like "can't fill rx buffer" in
> the log. The only kernel message being logged repeatedly is "card reports
> no resources".
Does the card actually receive packets?
If it doesn't receive anything, it's the second scenario.
If it receives packets, and complains only sometimes, at moments of traffic
bursts, it's the third situation: just too short buffer ring for your bursts.
Best regards
Andrey