debugnet_any_ifnet_update: Bad dn_init result on all Interfaces after update

Started by crissi, February 04, 2022, 05:46:53 PM

Previous topic - Next topic
Hello,

Updated to 22.1. ZFS Install with LAGG. Checking dmesg:


debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp 0xfffff800031f3000), ignoring.
igb1: link state changed to DOWN
lagg0: link state changed to DOWN
debugnet_any_ifnet_update: Bad dn_init result from igb2 (ifp 0xfffff8000505d800), ignoring.
igb2: link state changed to DOWN
debugnet_any_ifnet_update: Bad dn_init result from igb3 (ifp 0xfffff80003f25000), ignoring.
igb3: link state changed to DOWN

igb1: link state changed to UP
igb3: link state changed to UP
igb2: link state changed to UP
lagg0: link state changed to UP


Get the Bad dn_init on all Interfaces (Intel Interfaces), after the Update to OPNsense 22.1.

How to fix?
Thx!
Cheers,
Crissi

Me too !

debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp 0xfffff80003421000), ignoring

This was done in FreeBSD 13 to avoid a panic during boot... https://github.com/opnsense/src/commit/65366903c3a29

According to the commit the driver needs to be fixed which I assume never happened. Haven't seen an issue stemming from this particular message though.


Cheers,
Franco


Hi Franco,

thanks for the information. Just to understand, this means the messages get fixed in a new release?
Thx!
Cheers,
Crissi

The message is spurious if FreeBSD doesn't decide to refactor it anyway. I will propose a patch to FreeBSD and see what happens.


Cheers,
Franco