Re: eepro100 troubles

From: Brian (hiryuu@ztnet.com)
Date: Thu Jun 15 2000 - 03:14:47 EST


Day 3 and still going.

I guess it's worth noting that I have a PCI card while Scott's (I gather) is
integrated into the motherboard.

His comes up as:
eth0: Intel PCI EtherExpress Pro100 82557, 00:90:27:8D:36:FA, IRQ 21.
  Board assembly 000000-000, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.

Mine comes up as:
eth1: OEM i82557/i82558 10/100 Ethernet, 00:80:29:66:1A:82, IRQ 11.
  Board assembly 650990-001, Physical connectors present: RJ45
  Primary interface chip DP83840 PHY #1.
  DP83840 specific setup, setting register 23 to 8462.

I do, however, get a few huge streaks of stuff like this:
eth1: can't fill rx buffer (force 0)!
eth1: Tx ring dump, Tx queue 105081587 / 105081587:
eth1: 0 200ca000.
eth1: 1 000ca000.
eth1: 2 000ca000.
eth1: 3 000ca000.
eth1: 4 000ca000.
eth1: 5 000ca000.
eth1: 6 000ca000.
eth1: 7 000ca000.
eth1: 8 200ca000.
eth1: 9 000ca000.
eth1: 10 000ca000.
eth1: 11 000ca000.
eth1: 12 000ca000.
eth1: 13 000ca000.
eth1: 14 000ca000.
eth1: 15 000ca000.
eth1: 16 200ca000.
eth1: 17 000ca000.
eth1: 18 400ca000.
eth1: *=19 000ca000.
eth1: 20 000ca000.
eth1: 21 000ca000.
eth1: 22 000ca000.
eth1: 23 000ca000.
eth1: 24 200ca000.
eth1: 25 000ca000.
eth1: 26 000ca000.
eth1: 27 000ca000.
eth1: 28 000ca000.
eth1: 29 000ca000.
eth1: 30 000ca000.
eth1: 31 000ca000.
eth1: Printing Rx ring (next to receive into
106439943, dirty index 106439942).
eth1: 0 00000001.
eth1: 1 00000001.
eth1: 2 00000001.
eth1: 3 00000001.
eth1: 4 00000001.
eth1: l 5 c0000001.
eth1: * 6 00000000.
eth1: = 7 0000a020.
eth1: 8 0000a020.
eth1: 9 00000001.
eth1: 10 00000001.
eth1: 11 00000001.
eth1: 12 00000001.
eth1: 13 00000001.
eth1: 14 00000001.
eth1: 15 00000001.
eth1: 16 00000001.
eth1: 17 00000001.
eth1: 18 00000001.
eth1: 19 00000001.
eth1: 20 00000001.
eth1: 21 00000001.
eth1: 22 00000001.
eth1: 23 00000001.
eth1: 24 00000001.
eth1: 25 00000001.
eth1: 26 00000001.
eth1: 27 00000001.
eth1: 28 00000001.
eth1: 29 00000001.
eth1: 30 00000001.
eth1: 31 00000001.

I'm not sure what's useful in that. This morning's incident produced about
300k worth of it in the span of 4 seconds. Force is 1 or 0 with no apparent
pattern and the l, *, and = usually advance one or two places between dumps.

I don't have any traffic reports fine-grained enough to say if it stopped
responding during the incident, but it doesn't seem to have any long term
effect.

This is a 256MB Celeron/450 that gets pretty hammered (probably around 7-8
Mbit at that time of day).

        -- Brian

On Mon, 12 Jun 2000, Brian wrote:
> So Scott... if possible, get a second, non-intel card in that server and
> setup a static route between the server and some other box using that
> second card. If only the NIC hangs, you can come in that static route to
> ifup/ifdn the card and check out the logs.
>
> Meanwhile, I'm going to try 1.20.2.10.
> On my system, it took the older drivers 1.5 days to hang, so I'll let you
> know Tuesday.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu



This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:41 EST