From owner-freebsd-net@freebsd.org Wed Apr 21 18:04:24 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A867F5ED9C6 for ; Wed, 21 Apr 2021 18:04:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FQT2w48cSz3rS0 for ; Wed, 21 Apr 2021 18:04:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8E6AA5EDA49; Wed, 21 Apr 2021 18:04:24 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8E30C5EDA48 for ; Wed, 21 Apr 2021 18:04:24 +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 4FQT2w35k2z3rVF for ; Wed, 21 Apr 2021 18:04:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 5D7672840 for ; Wed, 21 Apr 2021 18:04:24 +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 13LI4OLE001005 for ; Wed, 21 Apr 2021 18:04:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13LI4OBa001004 for net@FreeBSD.org; Wed, 21 Apr 2021 18:04:24 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: net@FreeBSD.org Subject: [Bug 235524] igb(4): Ethernet interface loses active link state Date: Wed, 21 Apr 2021 18:04:23 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mack@ifis.cs.tu-bs.de X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? mfc-stable11? X-Bugzilla-Changed-Fields: cc 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 MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2021 18:04:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235524 mack@ifis.cs.tu-bs.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mack@ifis.cs.tu-bs.de --- Comment #10 from mack@ifis.cs.tu-bs.de --- Same problem here from time to time on a four port realtek card (re0, re1 currently used). Machine is used as a router and it now happened three times that the interf= aces somehow get shut off - not seen, what the real problem is, as we had to hav= e it up and running very quickly, so an immediate reboot helped in all three cas= es. link state changes to DOWN / UP happens once or twice every minute, when we cannot receive any packets on both interfaces, even though only one interfa= ce is logged with this problem. This switching down and up again happens every now and then without further impact. Time between DOWN and UP message is four seconds quite consistently= . Is seems to be triggered from a watchdog timeout (kernel: re0: wathcdog timeou= t). Maybe the problem gets triggered by (too?) much network traffic, as the net= work traffic was probably higher during those three cases. Btw.: someone mentioned of similar problems when pf was enabled and no problems, when pf was disabled. We are running ipfilter on that machine, so= it might be possible that filtering and high traffic promotes these problems, regardless of the network card used. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=