What could be reason for Tx packet error in ifconfig output


I am working with MAC to MAC MII link in my embedded board. one end of link has MPC8569 processor (free scale) and other side has BCM68610 controller (broadcom). I am trying to ping my switch from my processor but I am not able to do so.

after doing ping, I noticed tx packet error in ifconfig output.

[root@Device ~]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 76:00:00:98:74:1A  
          inet addr:  Bcast:  Mask:
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:12 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:504 (504.0 B)
          Base address:0x3200 

What could be the reasons for Tx packet error?

  1. from general networking point of view.
  2. from embedded system point of view.

This is direct connection between processor and controller so there can not be a netweok cognition problem. from what I guess, this could be due to some configuration problem of connection but I am not able to figure that out.

This is my ethtool output.

[root@Device ~]# ethtool eth1
Settings for eth1:
        Supported ports: [ ]
        Supported link modes:   1000baseT/Full 
        Supports auto-negotiation: No
        Advertised link modes:  1000baseT/Full 
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: external
        Auto-negotiation: off
        Current message level: 0x0000003f (63)
        Link detected: yes
asked on Super User Jan 30, 2015 by saurabh agarwal

0 Answers

Nobody has answered this question yet.

User contributions licensed under CC BY-SA 3.0