RE: eth0: card reports no resources

> That's a modified version of a modified driver...

I didn't do it!!!  I just inherited the box! ;)

> > > What is the incoming packet rate?
> >
> > Unsure, since the console becomes extremely lagged during
> this time.  We
>
> That makes it difficult to figure out if you are getting a
> high incoming
> packet rate, or if there are a small number packets such as
> "frag bombs"
> that consume disproportionate CPU time.

Do you have any suggestions on something that we can keep running on the
console for when this happens?  A command-line tool to see the packet rate?

> > > Have you increased the VM parameters as previously
> suggested on this list?
> >
> > I am doing that as soon as I understand what I am changing,
> and how to do it
> > properly (in /proc/sys/vm/bdflush), yes.
>
> Yes, it's very difficult to find info on what the parameters are, what
> they do, and suggested settings for different circumstances.
> You would
> think that anyone that changes the interface should also be
> responsible
> for documenting the new interface, but that's not how it works...
>
> The best guide I've found, without just reading the source code, is
> http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-R
H-Edition-v1.3/chap6sec68.html

That is the exact book I have at home and will be referencing!  It was worth
the money (very low price for download) for the newer one.

> One thing I -am- seeing is a ton of frame errors on the nic:
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2616981 errors:0 dropped:0 overruns:0 frame:46855

What is reported in /proc/net/dev?  The 'ifconfig' program reads the raw
values from there, and then discards or summarizes the error fields.  We
need to know what type of errors these are.


[root@sieve /root]# cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
<...>
  eth0:660772930 4104383    0    0    0 59664          0         0
3118239436 6135247    0    0    0     0       0          0
<...>

Holy crap!  I just did it 10 secs after doing that and got:

  eth0:663099751 4132672    0    0    0 96432          0         0
3175953300 6180075    0    0    1     0       0          0


If you are using a recent version of my driver release, you can
selectively enable driver status/error messages using
  mii-diag  eth0 --msg-level <value>

That doesn't work, so I am guessing I have an older version?


[root@sieve /root]# ./mii-diag -v
mii-diag.c:v2.00 4/19/2000  Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
 MII PHY #1 transceiver registers:
   2100 780d 02a8 0154 05e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0203 0000 0001 b98a 0000 0026 8273 0018
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x2100: Auto-negotiation disabled, with
 Speed fixed at 100 mbps, full-duplex.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Link partner information information is not exchanged when in fixed speed
mode.
 MII PHY #1 transceiver registers:
   2100 780d 02a8 0154 05e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0a03 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x2100: Auto-negotiation disabled!
   Speed fixed at 100 mbps, full-duplex.
 Basic mode status register 0x780d ... 780d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:aa:00:--:--:--, model 21 rev. 4.
   No specific information is known about this transceiver type.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.