From owner-freebsd-stable@freebsd.org Sun Oct 4 19:20:04 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 549F5A10737 for ; Sun, 4 Oct 2015 19:20:04 +0000 (UTC) (envelope-from lists@searchy.net) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id DCF061A05 for ; Sun, 4 Oct 2015 19:20:03 +0000 (UTC) (envelope-from lists@searchy.net) Received: from [192.168.5.21] (5418453B.cm-5-1b.dynamic.ziggo.nl [84.24.69.59]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id 9C5831E8C07; Sun, 4 Oct 2015 19:19:55 +0000 (UTC) Message-ID: <56117BD8.10806@searchy.net> Date: Sun, 04 Oct 2015 21:19:52 +0200 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: Jack Vogel CC: FreeBSD Stable Subject: Re: em0 and em1 watchdog timed out References: <560EC0C6.409@searchy.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Oct 2015 19:20:04 -0000 FreeBSD 10.2 r286666 . The drivers is Intel(R) PRO/1000 Network Connection 7.4.2 I will start some tests without lagg configured. Regards, Frank de Bot Jack Vogel wrote: > You missed the all-important details: OS version, driver version. > And another question I can think of, do these interfaces watchdog if they > are not configured with lagg? > > Cheers, > > Jack > > > On Fri, Oct 2, 2015 at 10:37 AM, Frank de Bot (lists) > wrote: > >> On a server I have 2 interfaces configured in a lagg. It seemed to be >> running stable until now (about a week), both interfaces repeatable go >> down after a watchdog timeout. >> >> Output from /var/log/messages >> >> Oct 2 10:15:11 nas kernel: em0: Watchdog timeout Queue[0]-- resetting >> Oct 2 10:15:11 nas kernel: Interface is RUNNING and ACTIVE >> Oct 2 10:15:11 nas kernel: em0: TX Queue 0 ------ >> Oct 2 10:15:11 nas kernel: em0: hw tdh = 804, hw tdt = 905 >> Oct 2 10:15:11 nas kernel: em0: Tx Queue Status = -2147483648 >> Oct 2 10:15:11 nas kernel: em0: TX descriptors avail = 915 >> Oct 2 10:15:11 nas kernel: em0: Tx Descriptors avail failure = 0 >> Oct 2 10:15:11 nas kernel: em0: RX Queue 0 ------ >> Oct 2 10:15:11 nas kernel: em0: hw rdh = 912, hw rdt = 911 >> Oct 2 10:15:11 nas kernel: em0: RX discarded packets = 0 >> Oct 2 10:15:11 nas kernel: em0: RX Next to Check = 912 >> Oct 2 10:15:11 nas kernel: em0: RX Next to Refresh = 911 >> Oct 2 10:15:11 nas kernel: em0: link state changed to DOWN >> Oct 2 10:15:13 nas kernel: em0: link state changed to UP >> Oct 2 10:15:13 nas devd: Executing '/etc/rc.d/dhclient quietstart em0' >> Oct 2 10:21:56 nas kernel: em1: Interface stopped DISTRIBUTING, >> possible flapping >> Oct 2 10:21:59 nas kernel: em1: Watchdog timeout Queue[0]-- resetting >> Oct 2 10:21:59 nas kernel: Interface is RUNNING and ACTIVE >> Oct 2 10:21:59 nas kernel: em1: TX Queue 0 ------ >> Oct 2 10:21:59 nas kernel: em1: hw tdh = 686, hw tdt = 806 >> Oct 2 10:21:59 nas kernel: em1: Tx Queue Status = -2147483648 >> Oct 2 10:21:59 nas kernel: em1: TX descriptors avail = 896 >> Oct 2 10:21:59 nas kernel: em1: Tx Descriptors avail failure = 0 >> Oct 2 10:21:59 nas kernel: em1: RX Queue 0 ------ >> Oct 2 10:21:59 nas kernel: em1: hw rdh = 167, hw rdt = 166 >> Oct 2 10:21:59 nas kernel: em1: RX discarded packets = 0 >> Oct 2 10:21:59 nas kernel: em1: RX Next to Check = 167 >> Oct 2 10:21:59 nas kernel: em1: RX Next to Refresh = 166 >> Oct 2 10:21:59 nas kernel: em1: link state changed to DOWN >> Oct 2 10:22:02 nas kernel: em1: link state changed to UP >> Oct 2 10:22:02 nas devd: Executing '/etc/rc.d/dhclient quietstart em1' >> >> it seems to occur when the interface are loaded. On the same server I >> also have a PCI card, the same issue occurs here. em0 and em1 are both >> onboard 80003ES2LAN. the PCI card is 82571EB. >> >> I've found different threads, but I couldn't manage to find a fix for >> this. >> >> What else can be wrong? >> >> Regards, >> >> Frank de Bot >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >