From owner-freebsd-net@freebsd.org Tue Apr 28 01:46:50 2020 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 52D582CECD8 for ; Tue, 28 Apr 2020 01:46:50 +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 49B4JB1b1sz43YQ for ; Tue, 28 Apr 2020 01:46:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 366B22CECD7; Tue, 28 Apr 2020 01:46:50 +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 3633E2CECD6 for ; Tue, 28 Apr 2020 01:46:50 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49B4JB0mNyz43YP for ; Tue, 28 Apr 2020 01:46:50 +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) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 150B11C5A0 for ; Tue, 28 Apr 2020 01:46:50 +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 03S1knxQ003880 for ; Tue, 28 Apr 2020 01:46:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 03S1kn6f003878 for net@FreeBSD.org; Tue, 28 Apr 2020 01:46:49 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: Tue, 28 Apr 2020 01:46:49 +0000 X-Bugzilla-Reason: CC AssignedTo 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: ports.maintainer@evilphi.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: 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.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2020 01:46:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235524 Mel Pilgrim changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ports.maintainer@evilphi.co | |m --- Comment #7 from Mel Pilgrim --- I believe this is still recurring, even on 12.1-R, and that pf is involved somehow. Every few weeks, a server will go offline. When I bring up the management console, the link light is off and the console is full of errors like this: igb1: Watchdog timeout (TX: 2 desc avail: 42 pidx: 504) -- resetting igb1: Watchdog timeout (TX: 2 desc avail: 1024 pidx: 0) -- resetting With the first occurring once, then the second repeating every 2-3 seconds. If I ifconfig down the interface, the watchdog timeout errors cease and the link light comes on. If I then ifconfig up the interface the link light go= es off again and the watchdog timeout errors resume. Thus far, only rebooting fixes this state. Anecdote: this behaviour seems to correlate to whether or not pf is in use.= I have multiple of this exact hardware (Supermicro X11SSH-LN4F), some run pf, some don't. The behaviour occurs on every machine running pf, and none of t= he ones not running pf. It wasn't occurring on two machines for months, then = pf was enabled, and the behaviour started. It was occuring on one of the mach= ines running pf, then pf was disabled, and after months it has not recurred. I'm posting this here because the observation--the paradoxical if up/down behaviour fixed only with a reboot--is the same, and I have machines running 12.x that do it, suggesting this has only been partially masked. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=