Re: debugnet_any_ifnet_update: Bad dn_init result

2025-01-26 Thread Bjoern A. Zeeb
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 (

Re: debugnet_any_ifnet_update: Bad dn_init result

2022-03-07 Thread Eric Joyner
On Mon, Feb 28, 2022 at 7:01 AM Franco Fichtner wrote: > Hi Mark, > > On 28. Feb 2022, at 15:51, Mark Johnston 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

Re: debugnet_any_ifnet_update: Bad dn_init result

2022-02-28 Thread Franco Fichtner
Hi Mark, > On 28. Feb 2022, at 15:51, Mark Johnston 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: port 0x4000-0x401f mem 0xf7d

Re: debugnet_any_ifnet_update: Bad dn_init result

2022-02-28 Thread Mark Johnston
On Mon, Feb 07, 2022 at 12:57:40PM +0100, 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_updat