Showing results for 
Show  only  | Search instead for 
Did you mean: 
Registered: ‎10-31-2018

macb driver backporting

Hi all,

Recently I tested my zcu104 board on an L2 network switch that supports 100Mbits/Half duplex. When I stress tested the interface with the following command on my host pc, the 2018.3 pre-built image experienced a kernel panic (run "iperf3 -s" on zcu104):


iperf3 -c <zcu104_ip_addr> -t 500


It shows basically the same symptom as macb kernel driver bug at 10 mbps speed cause system to fail petalinux 2018.3 for zcu102 and custom board (sadly nobody responded); with the same message:


  185.785014] macb ff0e0000.ethernet eth0: BUG: halt tx timed out


I played with a few petalinux pre-built images, noticed that xilinx-v2019.1 did not fix the issue (it doesn't panic anymore, but eth0 will stop responding to all network requests and will not recover from it), but xilinx-v2020.2 has it mostly fixed (it still shows BUG: halt tx timed out occasionally,  but it no longer halts the eth0 and everything still works fine).

Since I would like to keep using 2018.3; would it be a good idea to backport the driver to 2018.3? I found a moderator suggest against backporting 2018.3 stuff to 2017.x in How safe it is to change the kernel version in Petalinux, I wonder backporting 2020.2 to 2018.3 is equally bad?

Moreover, if it is OK to backport, what is my easiest way to get started? If I shouldn't backport, how should I fix this issue on 2018.3?


Edit: formatting, readability, typo

0 Kudos
0 Replies