lkml.org 
[lkml]   [2000]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: eepro100 status?
Hello,

On Fri, Aug 25, 2000 at 04:49:55PM -0700, Thomas Davis wrote:
> Andrey Savochkin wrote:
> > There are different reasons for "no resource" reports.
> > The first possible is a big traffic bursts exhausting the whole RX ring.
> > This cases are rare.
>
> Is this case really rare?
>
> I've got a machine that worked great w/eepro 100, with kernel 2.2.13. I
> updated to 2.2.16 (bug fixes and other things), and I now have it going
> to sleep on the network on me.
>
> I've had 13 of 'eth0: card reports no resources.' in just 7 hours of
> uptime, and the following network load:
>
[snip]
> eth0 Link encap:Ethernet HWaddr 00:90:27:8D:28:F6
> inet addr:128.55.129.108 Bcast:128.55.131.255
> Mask:255.255.252.0
> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> RX packets:29098241 errors:13 dropped:0 overruns:7 frame:0
> TX packets:8726756 errors:18 dropped:0 overruns:13 carrier:0

The error rate of .0002% is not so bad, is it? :-)
However, you may do something if it bothers you.
First of all, check that you don't get "can't fill rx buffer" messages.
Then, increase RX ring size constant in the driver.

Best regards
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [from the cache]
©2003-2011 Jasper Spaans