From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 00:06:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 413C316A403 for ; Fri, 15 Sep 2006 00:06:10 +0000 (UTC) (envelope-from myers@aedifice.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.192.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2ACF43D45 for ; Fri, 15 Sep 2006 00:06:09 +0000 (GMT) (envelope-from myers@aedifice.net) Received: from veetwin.aedifice.net (c-24-6-65-32.hsd1.ca.comcast.net[24.6.65.32]) by comcast.net (rwcrmhc12) with ESMTP id <20060915000609m1200robr8e>; Fri, 15 Sep 2006 00:06:09 +0000 Received: from [10.0.0.20] (nazirite [10.0.0.20]) by veetwin.aedifice.net (8.13.8/8.13.1) with ESMTP id k8F068CJ094913; Thu, 14 Sep 2006 17:06:09 -0700 (PDT) (envelope-from myers@aedifice.net) Message-ID: <4509EE70.1040907@aedifice.net> Date: Thu, 14 Sep 2006 17:06:08 -0700 From: "David C. Myers" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051128) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> In-Reply-To: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) 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, 15 Sep 2006 00:06:10 -0000 > watchdogs mean that the transmit ring is not being cleaned, so the > question is what is your machine doing at 100% cpu, if its that busy > the network watchdogs may just be a side effect and not the real > problem? I get them with a completely idle machine. My home directory is mounted via NFS (from FreeBSD 6.1 on an amd64 machine), and with the kernel from earlier this week, the machine would just hang for 30 seconds to a couple of minutes. A slew of "watchdog timeout" messages would appear. Then I'd get a moment's responsiveness out of the machine, then another long wait, then a moment's responsiveness, then a long wait... The machine would never recover from this cycle (at least, so far as I was patient enough to wait). Going back to a kernel dated late July resolved everything. Someone else asked me for the hardware version of my em0 board... em0@pci2:10:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class = network subclass = ethernet -David.