On Mon, 7 Feb 2022, Franco Fichtner wrote:
Hi,
Looking at https://cgit.freebsd.org/src/commit/?h=65366903c3a29
and seeing it is still the case in stable/13 would it make sense to
remove the printf() as it seems to be irritating users...
debugnet_any_ifnet_update: Bad dn_init result from igb0
ues 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
> 0xf800035ea000), ignoring.
>
> Context for dn_init
queues/slots: TX 4/1024, RX 4/1024
debugnet_any_ifnet_update: Bad dn_init result from igb2 (ifp
0xf800035ea000), 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
0xf80003752800
rritating users...
>
> debugnet_any_ifnet_update: Bad dn_init result from igb0 (ifp
> 0xf80003663800), ignoring.
> debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp
> 0xf800038b9800), ignoring.
>
> So far the only reports are for igb(4).
Do you have any idea what triggers the message in
Hi,
Looking at https://cgit.freebsd.org/src/commit/?h=65366903c3a29
and seeing it is still the case in stable/13 would it make sense to
remove the printf() as it seems to be irritating users...
debugnet_any_ifnet_update: Bad dn_init result from igb0 (ifp
0xf80003663800), ignoring
