From nobody Mon Aug 02 17:51:46 2021 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 3740211FFFD9 for ; Mon, 2 Aug 2021 17:51:59 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gdlv23Yw8z4lC3 for ; Mon, 2 Aug 2021 17:51:58 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-yb1-xb33.google.com with SMTP id j77so27805702ybj.3 for ; Mon, 02 Aug 2021 10:51:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=39e90cbd7Ren02DfBrq3whWKO/7fbURyrZYC/qL9tFY=; b=Q6geustkr245IUUvP21PDOfxMSUajxSKgn9Kal0JQYF5n4f11EVm7wGIqwA036d5yz y3ClvEJCm98z+Q2ALZ2ogi8mZpgXf4B9hlZhaltKnSY32TY8GFt7Rgl0etEUWpP184Rh FK/yXPYKs3fvmedhDP3rs93BLGXNtldXtCnSg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=39e90cbd7Ren02DfBrq3whWKO/7fbURyrZYC/qL9tFY=; b=AhR6fChX8hwM8/FTTpHMBV5Xc9Jj5HRuJb+nCDPVeCFsfsBHYhDmr2sDNyD6g9A2bp 9NeelLThs8+BT5Oec3PII6ioXANFqAwlzGXnXfA9SW+SjothUu01qb997DFyznckZFoF hIv5emfj/6Pz+XfT/OUQK2XjAw3CuIraktQ0ysFdctm/duO/ld7lYC7dUxWGYX6dND3W zlYtHwbOlN2iozDJDd0R4Vrax0sB8GkPlMv4Mdua0WSjDgjUd9pWHMUfXLK8mrzT1za7 sfuKczPv5ij/fj+mAVfZ6kshB0fgg93QN077bJ59A5wATUIvEfzFq1ZTWyAWUhmJUUNk OQGQ== X-Gm-Message-State: AOAM533dSJTqvGRRpjR93r7U7Jk5CybEoUMSPx28kNBED8mnGiLJp6vg sw/zyJwO36Ydo/DJw1FyHz9bNGAJvvM97RN0rR7/ZxAoyloiFg== X-Google-Smtp-Source: ABdhPJyLyQt2KSIiWbxXw5YZO89wToD8W9LTgYPP22PqFZ3Apd0XrkbDXx+YpaliQY4s8Jv+dTAuIYu+OTaQWNZak/4= X-Received: by 2002:a25:ba10:: with SMTP id t16mr22068553ybg.87.1627926717747; Mon, 02 Aug 2021 10:51:57 -0700 (PDT) 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 From: Kevin Bowling Date: Mon, 2 Aug 2021 10:51:46 -0700 Message-ID: Subject: igb(4) and VLAN issue? To: FreeBSD Net Cc: Franco Fichtner Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Gdlv23Yw8z4lC3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=kev009.com header.s=google header.b=Q6geustk; dmarc=none; spf=pass (mx1.freebsd.org: domain of kevin.bowling@kev009.com designates 2607:f8b0:4864:20::b33 as permitted sender) smtp.mailfrom=kevin.bowling@kev009.com X-Spamd-Result: default: False [-0.95 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-0.86)[-0.860]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; DMARC_NA(0.00)[kev009.com]; NEURAL_SPAM_MEDIUM(0.21)[0.209]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[kev009.com:~]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b33:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_PERMFAIL(0.00)[kev009.com:s=google]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi, I caught wind that an igb(4) commit I've done to main and that has been in stable/12 for a few months seems to be causing a regression on opnsense. The commit in question is https://cgit.freebsd.org/src/commit/?id=eea55de7b10808b86277d7fdbed2d05d3c6db1b2 The report is at: https://forum.opnsense.org/index.php?topic=23867.0 I haven't heard of this issue elsewhere and cannot replicate it on my I210s running main. I've gone over the code changes line by line several times and verified all the logic and register writes and it all looks correct to my understanding. The only hypothesis I have at the moment is it may be some subtle timing issue since VLAN changes unnecessarily restart the interface on e1000 until I push in a work in progress to stop doing that. I'd like to see the output of all the processes or at least the process configuring the VLANs to see where it is stuck. Franco, do you have the ability to 'control+t' there or otherwise set up a break into a debugger? Stacktraces would be a great start but a core and a kernel may be necessary if it isn't obvious. Regards, Kevin