From nobody Sat Apr 15 08:47:59 2023 X-Original-To: bugs@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 4Pz6Ql3ng7z44vGR for ; Sat, 15 Apr 2023 08:47:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pz6Ql28cRz3L1p for ; Sat, 15 Apr 2023 08:47:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681548479; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rtIkThaztDTaYsAOcDpiLR7Aq24bO1j3zpbYIeRUoZo=; b=MtYgGrBFVMim1Ibz2RjBSfpzZ2P0ubAtOE/7pw6s8vdR8AMAiwlE7j+JDnlFKmFI0cmMp2 XqWfgMWftljL4GYrUq7IBpXniywJcgos7BOVn2eWV7+7IaURAFN3+hiWbLlMr5aHuE+399 1VN19j6Rp1AHeXvlsxW3Q36R/wPg7fbz8Azaf946VK999x0NR7FwDgmYIfvdbAt8VL/t2V BEFcyF5UB1NJYLfnty1qBfAGDrRKv29k2IDBLGTi7lBQCfDwpXKwbELwsZyumouXTF409x /Gwm3LU9H3qEZQ7cBVYGhyD9GbsEGNzBdDEt8JkxZtzeEZpsh00sgGA+BO2GEg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681548479; a=rsa-sha256; cv=none; b=I33XqKv5soRlW01Vo3xOHC2hRikLpiI7renNTm/VVtWNFEGeS5d2pMMH4A1IQYR6Bz25N2 MyxRHd3myQA0Y2UWkH0bvyvODd7LdvdsQxBuRm1P52IhU4iYTvCOsL9KN8C1GSUNRU8ZTF PRUD1/creQlhbywfujG+VELNC22aLijH6tC73jNzzzg2eCPn7GRK7PNbhIzpGOqr/vbmY/ iy85bb3nzGObQVRsVfNzTipuEHfSXQeO4XEvV6D9Y4wxWx3dQuaCsURspVPtNI1e2OdbY0 X3qhLcdcN0SQCFRIDnxrt92wOHpUJPLl4YmkeA32c0XrnTfk18foiAjf/KWwIg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Pz6Ql0wSbz10JP for ; Sat, 15 Apr 2023 08:47:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 33F8lx6x088586 for ; Sat, 15 Apr 2023 08:47:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 33F8lxMX088584 for bugs@FreeBSD.org; Sat, 15 Apr 2023 08:47:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch Date: Sat, 15 Apr 2023 08:47:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260260 --- Comment #7 from Marek Zarychta --- No idea. Perhaps I am wrong. Now I recall that transitioned to stable/13 on affected machines relatively late, and the bug was reported here even later= . I wonder if lagg(4) has anything to do with it, since in the report of bug 268490, using lagg(4) has also been noted. I am utilising lagg on all affec= ted setups, think I can check if it's lagg dependent this weekend. --=20 You are receiving this mail because: You are the assignee for the bug.=