ci/a618: intermittent network failure
2022-06-15 11:37:03.269031: [ 1731.550367] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:08.417505: [ 1732.574483] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:08.417734: [ 1733.599402] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:08.417791: [ 1733.604506] nfs: server 192.168.201.1 not responding, still trying
2022-06-15 11:37:08.417810: [ 1733.611246] nfs: server 192.168.201.1 not responding, still trying
2022-06-15 11:37:08.417825: [ 1734.622710] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:08.417841: [ 1735.646494] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:08.417856: [ 1736.670695] r8152 2-1.3:1.0 eth0: Tx status -71
2022-06-15 11:37:13.552266: [ 1736.675721] nfs: server 192.168.201.1 not responding, still trying
2022-06-15 11:37:13.552385: [ 1736.682431] nfs: server 192.168.201.1 not responding, still trying
https://gitlab.freedesktop.org/mesa/mesa/-/jobs/24086547
I've seen this a few times, would be good to detect and reboot.