TK1 ethernet connection failure

Hello,
Some of our TK1 boards (1 out of 10) shows the errors listed below. For some reason the ethernet connection goes up and down and because of this we cannot communicate with the device. However when we force the ethernet speed to fullspeed the issue does not show up - but this is not suitable solution for us. Any help would be much appreciated. BR

Setup:
Apalis TK1 V1.2A
Ixora V1.2
BSP3.0 with mainline kernel 5.4

[ 284.095847] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 285.161181] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 287.570664] igb 0000:02:00.0: exceed max 2 second
[ 287.575886] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 288.671127] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 291.090737] igb 0000:02:00.0: exceed max 2 second
[ 291.096003] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 298.081134] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 300.490660] igb 0000:02:00.0: exceed max 2 second
[ 300.495886] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 306.391100] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 308.800648] igb 0000:02:00.0: exceed max 2 second
[ 308.806334] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 313.151112] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 315.560660] igb 0000:02:00.0: exceed max 2 second
[ 315.565887] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 316.621113] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 319.030542] igb 0000:02:00.0: exceed max 2 second
[ 319.035691] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 320.110990] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 322.520663] igb 0000:02:00.0: exceed max 2 second

Hi @qojote ,

Thanks for using the Toradex community.

We have seen this behaviour on other occasions before.

We recommend the following:

  • Change the cables with which you connect the module
  • Test if it works now
  • If it does not → Exchange the carrier
  • Test again
  • If it still does not work, reach out again and we look at the further steps

Best Regards
Kevin