From owner-freebsd-stable@FreeBSD.ORG Thu May 3 20:32:54 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 AB39216A403 for ; Thu, 3 May 2007 20:32:54 +0000 (UTC) (envelope-from sven@dmv.com) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.freebsd.org (Postfix) with ESMTP id 485AA13C4BB for ; Thu, 3 May 2007 20:32:54 +0000 (UTC) (envelope-from sven@dmv.com) Received: from mail-gw-cl-a.dmv.com (mail-gw-cl-a.dmv.com [216.240.97.38]) by smtp-gw-cl-c.dmv.com (8.12.10/8.12.10) with ESMTP id l43KWq47043234; Thu, 3 May 2007 16:32:53 -0400 (EDT) (envelope-from sven@dmv.com) Received: from [216.240.97.46] (lanshark.dmv.com [216.240.97.46]) by mail-gw-cl-a.dmv.com (8.12.9/8.12.9) with ESMTP id l43KWquk011042; Thu, 3 May 2007 16:32:52 -0400 (EDT) (envelope-from sven@dmv.com) From: Sven Willenberger To: Michael Collette In-Reply-To: References: Content-Type: text/plain Date: Thu, 03 May 2007 16:36:26 -0400 Message-Id: <1178224586.15571.6.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.38 Cc: FreeBSD Stable Subject: Re: Another em0 watchdog timeout 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: Thu, 03 May 2007 20:32:54 -0000 On Tue, 2007-05-01 at 11:05 -0700, Michael Collette wrote: > I realize there is a previous thread discussing this, but my symptoms > seem to be a little bit different. Here's the stats... > > FreeBSD 6.2-STABLE #1: Fri Apr 27 17:28:22 PDT 2007 > > em0@pci13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 PM' > class = network > subclass = ethernet > em1@pci14:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > em0: port > 0x5000-0x501f mem 0xea300000-0xea31ffff irq 16 at device 0.0 on pci13 > em0: Ethernet address: 00:30:48:5c:cc:84 > em1: port > 0x6000-0x601f mem 0xea400000-0xea41ffff irq 17 at device 0.0 on pci14 > em1: Ethernet address: 00:30:48:5c:cc:85 > > I'm seeing the following entries in my messages log pop up about 2-4 > times a day... > > May 1 08:29:38 alpha kernel: em0: watchdog timeout -- resetting > May 1 08:29:38 alpha kernel: em0: link state changed to DOWN > May 1 08:29:41 alpha kernel: em0: link state changed to UP > > I've gone and added the DEVICE_POLLING option in the kernel, but this > doesn't seem to help. The problem only seems to happen during the > hours that my users would be hitting this box, so it really gets > noticed when those 3 seconds go by. And yes, it's almost always a 3 > second drop on the interface. > > Is there anything I can do to prevent this from happening? I saw > mention of a firmware update I might try, but haven't been able to > locate the file in question. > > Thanks, Search the list for a post by Jack Vogel that contains an attachment named "dcgdis.ThisIsZip". That firmware patch solved my em watchdog timeout issues.