NIC drops all packages

[Mark]

I re-installed the system, network cards are fine (for now).
Kudzu keeps the configuration, the cards work, no dropped packets any more.

BUT - the machine still locks up on me - seems randomly. Sometimes when I
call kudzu. Sometimes when I reboot shortly before or after the drives are
unmounted (don't remember exactly). It does this with and without the NIC
cards. I can't reproduce the behaviour. Will try to run it idle over the
weekend and see if it is still reacting on Monday morning.

Strange, strange...

MARK

> -----Original Message-----
> From: fedora-list-bounces at redhat.com 
> [mailto:fedora-list-bounces at redhat.com] On Behalf Of Bob Chiodini
> Sent: Friday, July 16, 2004 3:56 AM
> To: For users of Fedora Core releases
> Subject: Re: NIC drops all packages
> 
> 
> On Thu, 2004-07-15 at 14:04, Mark wrote:
> > Hi.
> > 
> > I have a 3 NICs in a system, 1 onboard and 2 tulip-driver cards.
> > The tulip cards are identical. The builtin one is eth0, the 
> two tulips are
> > eth1 and eth2.
> > They all go into the same switch and then on to the rest of 
> the LAN. All 3
> > LEDs on the switch are green. Eth2 has green and orange lights.
> 
> > Eth2 is dropping all packages, not one makes it through. I 
> get a bunch of
> > these messages:
> > Jul 15 10:42:59 lvd2 kernel: NETDEV WATCHDOG: eth2: 
> transmit timed out
> > Jul 15 10:42:59 lvd2 kernel: eth2: 21140 transmit timed out, status
> > f8922010, SIA 000003c0 ffff0001 fffbfb7f 8ff0c008, resetting...
> > Jul 15 10:42:59 lvd2 kernel: eth2: transmit timed out, switching to
> > 100baseTx-FDX media.
> > Jul 15 10:43:07 lvd2 kernel: NETDEV WATCHDOG: eth2: 
> transmit timed out
> > Jul 15 10:43:07 lvd2 kernel: eth2: 21140 transmit timed out, status
> > f8922010, SIA 000003c0 ffff0001 fffbfb7f 8ff5c008, resetting...
> > Jul 15 10:43:07 lvd2 kernel: eth2: transmit timed out, switching to
> > 10baseT-FDX media.
> > 
> 
> What do the LEDs an the switch indicate?
> 
> You did not say what brand of NIC the tulip cards are, if Linksys, the
> yellow LED might indicate a 100Mb/s link.  What does mii-tool tell you
> about eth2?
> 
> If you switch cables between eth1 and eth2 and correct the IP 
> addresses
> accordingly, does eth2 work?  If so, look for a cable or switch port
> problem.  If not then it's probably the NIC.
> 
> > Could the NIC be broken, or is this something else? Also, I 
> just noticed
> > that eth0 and eth1 both use IRQ 5. Is that ok?
> 
> Sharing the IRQ should be OK.
> 
> > Trying to ping an address in eth2's network comes back with network
> > unreachable
> > If I switch the addresses of eth0 and eth2 I can ping the 
> address that I
> > could not ping before.
> 
> Did you move the cables as well?  This sounds like, at least, the 101
> and 103 subnets are "connected" together at the switch.
> 
> I noticed your other post concerning the NMI.  Has kudzu stabilized as
> far as the internal NIC?  What is in your /etc/modules.conf?
> 
> Bob...
>