Re: debugnet_any_ifnet_update: Bad dn_init result

On Mon, Feb 28, 2022 at 7:01 AM Franco Fichtner <franco@opnsense.org> wrote:

> Hi Mark,
>
> On 28. Feb 2022, at 15:51, Mark Johnston <markj@freebsd.org> wrote:
>
> Do you have any idea what triggers the message in the first place?  I
> haven't seen it on my igb-using systems.
>
>
> No but I have hardware here that does this. Short dmesg scan:
>
> # dmesg | grep igb2
> igb2: <Intel(R) I210 Flashless (Copper)> port 0x4000-0x401f mem
> 0xf7d00000-0xf7d1ffff,0xf7d20000-0xf7d23fff irq 36 at device 0.0 on pci3
> igb2: NVM V0.6 imgtype6
> igb2: Using 1024 TX descriptors and 1024 RX descriptors
> igb2: Using 4 RX queues 4 TX queues
> igb2: Using MSI-X interrupts with 5 vectors
> igb2: Ethernet address: f4:90:ea:00:2d:9d
> igb2: netmap queues/slots: TX 4/1024, RX 4/1024
> debugnet_any_ifnet_update: Bad dn_init result from igb2 (ifp
> 0xfffff800035ea000), ignoring.
>
> Context for dn_init messages:
>
> # dmesg | grep -C1 dn_init
> igb0: link state changed to UP
> debugnet_any_ifnet_update: Bad dn_init result from igb0 (ifp
> 0xfffff80003752800), ignoring.
> igb1: link state changed to UP
> debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp
> 0xfffff800035e8800), ignoring.
> intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
> --
> amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
> debugnet_any_ifnet_update: Bad dn_init result from igb2 (ifp
> 0xfffff800035ea000), ignoring.
> lagg0: link state changed to DOWN
>
> It appears this happens on all interfaces that get configured during init.
>
> The device has a fourth device that doesn't appear to have this issue:
>
> # dmesg | grep igb3
> igb3: <Intel(R) I210 Flashless (Copper)> port 0x6000-0x601f mem
> 0xf7e00000-0xf7e1ffff,0xf7e20000-0xf7e23fff irq 40 at device 0.0 on pci4
> igb3: NVM V0.6 imgtype6
> igb3: Using 1024 TX descriptors and 1024 RX descriptors
> igb3: Using 4 RX queues 4 TX queues
> igb3: Using MSI-X interrupts with 5 vectors
> igb3: Ethernet address: f4:90:ea:00:2d:9e
> igb3: netmap queues/slots: TX 4/1024, RX 4/1024
> vlan1: changing name to 'igb3_vlan43'
> igb3: promiscuous mode enabled
>
> Can also share full dmesg if you want or deliver other info.
>
>
> Cheers,
> Franco
>

I'm all for removing that printf(). What are you supposed to do about a
"Bad dn_init result from ####", and what's the problem if it's ignored?

- Eric