Re: debugnet_any_ifnet_update: Bad dn_init result
"Bjoern A. Zeeb" <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.net |
|---|---|
| Message-ID | <[email protected]> |
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 (ifp 0xfffff80003663800), ignoring. > debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp 0xfffff800038b9800), ignoring. > > So far the only reports are for igb(4). I still see them on main these days with igb (and obviously boot-v): [13.542599] debugnet_any_ifnet_update: Bad dn_init result from igb1 (ifp 0xfffff80003789000), ignoring. [14.568307] debugnet_any_ifnet_update: Bad dn_init result from igb2 (ifp 0xfffff8000378a000), ignoring. I use igb0 to netboot so it is UP by definition. I looked at the code as I figured I want to know "what bad result" (either error code or otherwise) to see the comment there. Is it worth looking at it? I am not a debugnet consumer given it never grew IPv6 support to my best knowledge but this is likely a igb ordering issue? /bz -- Bjoern A. Zeeb r15:7