Linux-kernel mailing list archive 1998-25,: Trying to restart the transmitter...

# Trying to restart the transmitter...

Jeff Wiegley (jeff@la.usweb.com)
Fri, 26 Jun 1998 19:56:35 -0700

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: no sound in 107??"
- Previous message: Keith Owens: "Re: pre-patch-2.1.107 breaks kmod"

I have a server, running v2.0.34 and has an Intel EtherExpressPro/100B
NIC. It keeps giving me these errors...

Jun 26 18:38:47 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:38:47 server kernel: eth0: Trying to restart the transmitter...
Jun 26 18:38:49 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:38:49 server kernel: eth0: Trying to restart the transmitter...
Jun 26 18:38:49 server ypbind[297]: server2.la.usweb.com: RPC: Timed out
Jun 26 18:38:54 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:38:54 server kernel: eth0: Trying to restart the transmitter...
Jun 26 18:40:24 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:40:24 server kernel: eth0: Trying to restart the transmitter...
Jun 26 18:40:26 server ypbind[297]: server2.la.usweb.com: RPC: Timed out
Jun 26 18:40:28 server ypbind[297]: server2.la.usweb.com: RPC: Timed out
Jun 26 18:40:33 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:40:33 server kernel: eth0: Trying to restart the transmitter...
Jun 26 18:40:43 server kernel: eth0: Transmit timed out: status 0050 command 0000.
Jun 26 18:40:43 server kernel: eth0: Trying to restart the transmitter...

Does anybody know why these are happening? I have the machine connected
directly to an Intel 510T 10/100 switch. When I check the switch's port
statistics I get multiple link down event on the port the server is connected
to. I made sure all the cabling is good using a PentaScanner 350 and
everything passed well for 100BaseTx.

Also I tried a different port that server2 was on and never got errors
and sure enough the problematic server started generating link down events
for that port as well so it seems that all the cabling and connections are
fine and the linux/etherexpress/device driver is somehow hiccuping and
causing the card to go off line for a few seconds every minute or so.

I have tried stock 2.0.34 and I have tried 2.0.34 + Donald's newest EEPro100
drivers without any luck.

Does anybody know what is causing this problem or what I can do to fix this??

Thanks,

- Jeff Wiegley

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

- Next message: Alan Cox: "Re: no sound in 107??"
- Previous message: Keith Owens: "Re: pre-patch-2.1.107 breaks kmod"