On Mon, Jul 07, 2025 at 12:52:11PM +0800, Kevin Lo wrote:
> I finally got a bnx(4) and tested the results.
> 
> bnx0 at pci3 dev 0 function 0 "Broadcom BCM5709" rev 0x20: apic 2 int 16
> bnx1 at pci3 dev 0 function 1 "Broadcom BCM5709" rev 0x20: apic 2 int 17
> bnx0: address 00:0e:1e:xx:xx:xx
> brgphy0 at bnx0 phy 1: BCM5709, rev. 8
> bnx1: address 00:0e:1e:xx:xx:xx
> brgphy1 at bnx1 phy 1: BCM5709, rev. 8
> 
> After testing bnx(4), its behavior is similar to pcn(4).
> When running iperf -u -l0 -t0 -c 192.168.8.22, although OACTIVE is set and
> packet loss occurs when running ping, it doesn't stay stuck for long nor
> does it require resetting the interface with ifconfig.

Thanks Kevin.  Not sure why the issue does not occur on pcn and bnx.
Perhaps device-level behaviour is an important factor.
Except for ngbe, all affected drivers seem to be Intel ones.