From owner-freebsd-net@FreeBSD.ORG  Fri Jun 20 20:11:56 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DE60D1065673
	for <freebsd-net@freebsd.org>; Fri, 20 Jun 2008 20:11:56 +0000 (UTC)
	(envelope-from crapsh@monkeybrains.net)
Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11])
	by mx1.freebsd.org (Postfix) with ESMTP id D6E838FC20
	for <freebsd-net@freebsd.org>; Fri, 20 Jun 2008 20:11:56 +0000 (UTC)
	(envelope-from crapsh@monkeybrains.net)
Received: from monchichi.monkeybrains.net
	(adsl-76-195-162-74.dsl.pltn13.sbcglobal.net [76.195.162.74])
	(authenticated bits=0)
	by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id m5KKBuO7051960
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 20 Jun 2008 13:11:56 -0700 (PDT)
	(envelope-from crapsh@monkeybrains.net)
Message-ID: <485C0F07.7000408@monkeybrains.net>
Date: Fri, 20 Jun 2008 13:11:51 -0700
From: Rudy <crapsh@monkeybrains.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080310)
MIME-Version: 1.0
To: Jack Vogel <jfvogel@gmail.com>
References: <20080516185813.H866@logos.sky.od.ua>	<2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com>	<4853055C.2030303@MonkeyBrains.NET>	<48535A11.4020003@monkeybrains.net>	<48582C29.8030307@monkeybrains.net>
	<2a41acea0806191055w5e112b8bsa57a8db2b177adbe@mail.gmail.com>
In-Reply-To: <2a41acea0806191055w5e112b8bsa57a8db2b177adbe@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.93,
	clamav-milter version 0.93 on pita.monkeybrains.net
X-Virus-Status: Clean
Cc: freebsd-net@freebsd.org
Subject: Re: Seeking help understanding my "emX: watchdog timeout" messages
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2008 20:11:57 -0000

Jack Vogel wrote:
> Watchdog reset is an indication that the TX completion did not happen
> within a reasonable time, it can the symptom of a variety of problems.
> 
> You list a bunch of settings for polling, is this interface in POLLING
> mode?
> 

Yes, DEVICE_POLLING is in the kernel and kern.polling.enable=1.  I did not issue a
  "ifconfig em2 polling" and I see it running, so I assume that it is in POLLING mode.


em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=1db<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,POLLING,VLAN_HWCSUM,TSO4>
	ether 00:15:17:78:99:72
	inet 64.215.30.154 netmask 0xfffffffc broadcast 64.215.30.155
	media: Ethernet autoselect (1000baseTX <full-duplex>)
	status: active

Interestingly, I also get the watchdog timeouts on my em4 (motherboard 82573E NIC).

In a 24 hour period, I see 8 'watchdog timeout' events.  4 on em2 and 4 on em4.  Both are uplinks 
to different cisco switches which vlan those ports to fiber uplinks.

Thank you for your time Jack,
Rudy