Comment 4 for bug 1835054

Good news:

The module is *definitely* built and loads fine. Thanks!

Bad news:

The driver has some issues... Full boot log attached, but first of all, spot the delay:

...
[ 2.849454] mvpp2 MRVL0110:00 eth0: Using random mac address ee:ad:f4:3c:ad:cf
...
[ 2.932894] mvpp2 MRVL0110:01 eth1: Using random mac address 16:0c:52:c7:5a:cb
...
[ 2.946932] mvpp2 MRVL0110:01 eth2: Using random mac address 7a:b8:9a:01:af:46
...
[ 2.962885] mvpp2 MRVL0110:01 enamrvl110i1: renamed from eth1
...
[ 3.229057] mvpp2 MRVL0110:01 rename4: renamed from eth2
...
[ 3.504865] mvpp2 MRVL0110:00 enamrvl110i0: renamed from eth0
...
[ 5.334377] Virtual CRAT table created for CPU
[ 5.334414] Parsing CRAT table with 1 nodes
[ 5.334450] Creating topology SYSFS entries
[ 5.334512] Topology: Add CPU node
[ 5.334545] Finished initializing topology
[ 63.937562] systemd-udevd[201]: eth2: Worker [221] processing SEQNUM=1947 is taking a long time
[ 93.650969] systemd-udevd[221]: eth2: Failed to rename network interface 4 from 'eth2' to 'enamrvl110i1': File exists
[ 93.892377] raid6: neonx8 gen() 3687 MB/s
[ 93.940370] raid6: neonx8 xor() 3241 MB/s
[ 93.988376] raid6: neonx4 gen() 3112 MB/s
[ 94.036370] raid6: neonx4 xor() 2696 MB/s
[ 94.084377] raid6: neonx2 gen() 2644 MB/s
...

Then, the "rename4" interface gets IP over DHCP and things seems ok, until I start generating more traffic (like pulling a tarball from kernel.org)... Then the interface "hangs", ie. no more data gets in nor out, but without any messages in the kernel log.

For better or worse, these symptoms more or less match what I observed using Debian Buster installer over the weekend, so I suspect it's an issue with "my" firmware (I believe others made it work on Macchiatobin).

From the "missing driver" perspective, the problem has been fixed :-)