[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: TX errors, internal nic


On Sat, Feb 22, 2003 at 09:18:13PM -0800, Doug_The_Slug wrote:
> eth1      Link encap:Ethernet  HWaddr 00:50:BF:97:D9:18
>           inet addr:  Bcast:  Mask:
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:10330332 errors:4 dropped:0 overruns:0 frame:6
>           TX packets:0 errors:10247612 dropped:0 overruns:0 carrier:20345878
>           collisions:0 txqueuelen:100
>           RX bytes:2195996995 (2.0 GiB)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0x1400

which driver does this card use? How is it connected to your
network? If it is a switch, what do the diagnostic lights tell you?

Could you install the mii-diag package and post the output of the
mii-diag program? 

I have the strong impression that this is either a flakey link or
some el Cheapo card that has trouble negotiating a link speed with
the other end.

> why is TX at 0?  how is the nic transmitting anything to the internal
> network when TX is at 0?   and for some reason, it's putting in an error for
> each packet.  also, what is this carrier number, and why is it so high?
> this isn't really an emergency since everything is running and working as
> far as i can see, but i just found this bit odd.

What that carrier number means is something I could not really get
an answer to, so if someone else here knows, I would like to know
I have recently seen such behaviour with a via-rhine card that was
for some reason re-negotiating the link speed several times per hour
and sometimes lost connection for quite a while.

Ciao, Arne.
 ,``o. OpenBSD        -        Debian GNU/Linux        -        Solaris  >o)
>( ,c@ GPG 1024D/913C2F81 2000-10-11  Arne P. Boettger <apb@createx.de>  /\\
 ',,,' Fingerprint = 6ED9 9A64 CD8A EB6F D841  0391 2F08 8F86 913C 2F81 _\_V

Attachment: pgpdlOzr9wqZ1.pgp
Description: PGP signature

Reply to: