From nobody Mon Feb 28 15:00:15 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 480DC19E3910 for ; Mon, 28 Feb 2022 15:00:25 +0000 (UTC) (envelope-from franco@opnsense.org) Received: from mail.opnsense.org (mail.opnsense.org [IPv6:2001:1af8:4700:a129:100::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4K6k8770fBz4mM3; Mon, 28 Feb 2022 15:00:23 +0000 (UTC) (envelope-from franco@opnsense.org) Received: from localhost (mail.opnsense.org [127.0.0.1]) by mail.opnsense.org (Postfix) with ESMTP id 3E49C153846; Mon, 28 Feb 2022 16:00:16 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.opnsense.org Received: from mail.opnsense.org ([127.0.0.1]) by localhost (mail.opnsense.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0jwKm87p_qiH; Mon, 28 Feb 2022 16:00:16 +0100 (CET) From: Franco Fichtner DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opnsense.org; s=dkim; t=1646060416; bh=HlypY2HZpJY4n5370Y19j7pUwn1wdQ5JmyTylH5HgqQ=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=F1pSp35eIebN6sb2CYaeifzesXtnHKUbAvMlQbfUCw3n60jHJ4zN3cGRieE7dhzzu TyJRocj0xmwPk1BmkQLcKWVZm/lqpgFdCilMjLW/in4NDMH0GdRnX/FoEfxFy39sjq ofcoU1EK+RyFENikhZYuZ4yQsSN+cTJKR3PH8cHs= Message-Id: <304F739C-914D-4675-A60F-80C539830F0C@opnsense.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_16AD0AA7-7E8D-4BD4-B80B-5BD40C65350B" List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: debugnet_any_ifnet_update: Bad dn_init result Date: Mon, 28 Feb 2022 16:00:15 +0100 In-Reply-To: Cc: freebsd-net@freebsd.org To: Mark Johnston References: X-Rspamd-Queue-Id: 4K6k8770fBz4mM3 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=opnsense.org header.s=dkim header.b=F1pSp35e; dmarc=pass (policy=quarantine) header.from=opnsense.org; spf=pass (mx1.freebsd.org: domain of franco@opnsense.org designates 2001:1af8:4700:a129:100::2 as permitted sender) smtp.mailfrom=franco@opnsense.org X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[opnsense.org:s=dkim]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[opnsense.org:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[opnsense.org,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-net]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:60781, ipnet:2001:1af8::/32, country:NL]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_16AD0AA7-7E8D-4BD4-B80B-5BD40C65350B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Mark, > On 28. Feb 2022, at 15:51, Mark Johnston wrote: >=20 > 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 = 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: at device 20.0 on pci0 -- amdtemp0: 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: 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= --Apple-Mail=_16AD0AA7-7E8D-4BD4-B80B-5BD40C65350B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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
= --Apple-Mail=_16AD0AA7-7E8D-4BD4-B80B-5BD40C65350B--