From owner-freebsd-stable@FreeBSD.ORG Fri Apr 6 17:01:02 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CF3816A401 for ; Fri, 6 Apr 2007 17:01:02 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 59D6313C448 for ; Fri, 6 Apr 2007 17:01:02 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l36H0HTB051339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Apr 2007 10:00:18 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <46167CA2.7080700@errno.com> Date: Fri, 06 Apr 2007 10:00:18 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.9 (X11/20070208) MIME-Version: 1.0 To: LI Xin References: <46150E1A.9050900@claranet.nl> <2a41acea0704051118t5e7965f6m76ee26b6263bb9cc@mail.gmail.com> <46166ED5.6040003@delphij.net> In-Reply-To: <46166ED5.6040003@delphij.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Jack Vogel , Jiang Hong , Jasper Berlijn Subject: Re: em0 watchdog timeout with nfs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Apr 2007 17:01:02 -0000 LI Xin wrote: > Hi, Jack, > > Jack Vogel wrote: >>> em0@pci0:14:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 >>> hdr=0x00 > [...] >> The driver in 6.2 RELEASE fixed all known problems with >> watchdogs, other than REAL issues with the network/hardware. >> Have you tried installing that? > > A friend of mine has reported similar problem, with different em(4) > hardware. The server runs lighttpd on ufs, and the watchdog timeout > occurs no matter whether there is heavy traffic. > > Here is some pciconf -l output which can be interesting. > > [root@me /usr/local/etc]# pciconf -l|grep em > em0@pci5:0:0: class=0x020000 card=0x30a38086 chip=0x108b8086 rev=0x03 > hdr=0x00 > em1@pci6:5:0: class=0x020000 card=0x30a18086 chip=0x10768086 rev=0x05 > hdr=0x00 > > Should more debugging aid / information is needed to narrow down the > issue please let us know, thanks! I've reported similar problems multiple times w/o any response. My nic is onboard (no msi involved, no polling used): em0@pci2:1:0: class=0x020000 card=0x80f71043 chip=0x10198086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller (LOM)' class = network subclass = ethernet trouble% ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:9e:c0:e5 inet 10.0.0.248 netmask 0xffffff00 broadcast 10.0.0.255 media: Ethernet autoselect (1000baseTX ) status: active When I boot I also see massive #'s of link state transitions while dhclient fetches a lease. I've swapped cables, switch ports, etc. I can believe it might be a h/w failure but was hoping I could isolate the issue to be certain (don't like discarding the onboard nic). This is a very current HEAD and has been a problem for several months (all against HEAD). Sam