Ethernet port is not able to receive ping replay

jagrati_chaudhary · ‎08-14-2024

i upgraded my device from 4.1 to 5.6 kernel after that Ethernet link getting detect and i am able to assign IP(192.168.1.2) also but when i ping an IP( 192.168.1.1) from the device ,it is not able to get replay from other device i try using tcpdum on both device and i found the the device with 192.168.1.1 send replay of every ping but the upgrade device not showing any reply of ICMP request.even i use the same Ethernet port to boot device and tftp worked fine to boot device with new kernel.everything works fine in u-boot.
i am adding my ethtool output for the port with kernel 4.1 and 5.6 below.

with kernel 5.6

5.6.11
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: external
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: g
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
root /flash

with 4.1
Settings for lan:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: MII
PHYAD: 0
Transceiver: external
netlink error: Operation not permitted
Link detected: yes

there is a difference for "Supported pause frame use" and "Advertised pause frame use" is this can create any difference ?
adding tcpdum log for both device.

jagrati_chaudhary · ‎08-20-2024

hi @SebastianG
i found these errors rx-crc-errors, rx-fcs-errors, and rx-code-error using ethtool .

adding ethtool output below.
root /flash # ethtool -S eth0
NIC statistics:
rx-allocation-errors: 0
rx-large-frame-errors: 0
rx-short-frame-errors: 0
rx-non-octet-errors: 0
rx-crc-errors: 1019
rx-overrun-errors: 0
rx-busy-errors: 0
rx-babbling-errors: 0
rx-truncated-frames: 0
ethernet-bus-error: 0
tx-babbling-errors: 0
tx-underrun-errors: 0
tx-timeout-errors: 0
tx-rx-64-frames: 0
tx-rx-65-127-frames: 1061
tx-rx-128-255-frames: 0
tx-rx-256-511-frames: 0
tx-rx-512-1023-frames: 0
tx-rx-1024-1518-frames: 0
tx-rx-1519-1522-good-vlan: 0
rx-bytes: 70305
rx-packets: 1061
rx-fcs-errors: 1061
receive-multicast-packet: 0
receive-broadcast-packet: 0
rx-control-frame-packets: 0
rx-pause-frame-packets: 0
rx-unknown-op-code: 0
rx-alignment-error: 0
rx-frame-length-error: 0
rx-code-error: 1061
rx-carrier-sense-error: 0
rx-undersize-packets: 0
rx-oversize-packets: 0
rx-fragmented-frames: 0
rx-jabber-frames: 0
rx-dropped-frames: 0
tx-byte-counter: 0
tx-packets: 0
tx-multicast-packets: 0
tx-broadcast-packets: 0
tx-pause-control-frames: 0
tx-deferral-packets: 0
tx-excessive-deferral-packets: 0
tx-single-collision-packets: 0
tx-multiple-collision-packets: 0
tx-late-collision-packets: 0
tx-excessive-collision-packets: 0
tx-total-collision: 0
reserved: 0
tx-dropped-frames: 0
tx-jabber-frames: 0
tx-fcs-errors: 0
tx-control-frames: 0
tx-oversize-frames: 0
tx-undersize-frames: 0
tx-fragmented-frames: 0