From owner-freebsd-stable@freebsd.org Fri Oct 2 21:01:03 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 62508A0E918 for ; Fri, 2 Oct 2015 21:01:03 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4729111B for ; Fri, 2 Oct 2015 21:01:02 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wiclk2 with SMTP id lk2so49835293wic.0 for ; Fri, 02 Oct 2015 14:01:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BDzEPsKS/zTlHhGRiQQqRKRjSdQLaGLWOLSav6QAv2s=; b=obx7gDT40Ypw0C81jMxgF90E529l6oC9Iq+YexZeEqKoLjovMrSw+Nx2zZGnkbOd8M yiyeyg4/X74hCKlmvRgsCqVYMsZ3P3msxMDaVLq40+Z/hHF5+PVF+pUKR8SZ9b4RGwlX T0BxvVnNk4Jvjnw1Z2EzOcqmJEss5eaxMM1mydQVj9L+E1FpPeWVXGah8xPc2sjwVdmG mnJHTshtHLT2kd7KGTHsb6GIJjWwKEoLhe76GbAJeP6nGML2Or3QIds5pZE2rHmEUO6E pox5Mpo4Wayj0T5nfl8hLF2ipzCBJhkuV+oNmQcKiC2FNHhXIk8KRPhopz0/Er4wk18i BytA== MIME-Version: 1.0 X-Received: by 10.194.238.228 with SMTP id vn4mr18183029wjc.13.1443819661229; Fri, 02 Oct 2015 14:01:01 -0700 (PDT) Received: by 10.194.95.35 with HTTP; Fri, 2 Oct 2015 14:01:01 -0700 (PDT) In-Reply-To: <560EC0C6.409@searchy.net> References: <560EC0C6.409@searchy.net> Date: Fri, 2 Oct 2015 14:01:01 -0700 Message-ID: Subject: Re: em0 and em1 watchdog timed out From: Jack Vogel To: "Frank de Bot (lists)" Cc: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Fri, 02 Oct 2015 21:01:03 -0000 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" >