From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:25:30 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 7B1DF16A4E7 for ; Thu, 14 Sep 2006 23:25:30 +0000 (UTC) (envelope-from danolson@visi.com) Received: from conn.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62D5943DDF for ; Thu, 14 Sep 2006 23:25:23 +0000 (GMT) (envelope-from danolson@visi.com) Received: from [192.168.240.220] (danolson.dsl.visi.com [209.98.225.50]) by conn.mc.mpls.visi.com (Postfix) with ESMTP id 67C2881B2; Thu, 14 Sep 2006 18:25:20 -0500 (CDT) Message-ID: <4509E4CD.8050102@visi.com> Date: Thu, 14 Sep 2006 18:25:01 -0500 From: Dan Olson User-Agent: Thunderbird 1.5.0.5 (X11/20060729) 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: Thu, 14 Sep 2006 23:25:30 -0000 Jack Vogel wrote: > On 9/13/06, Ronald Klop wrote: > ... > >> Them manual page em(4) mentions trying another cable when the watchdog >> timeout happens, so I tried that. But it didn't help. >> Is there anything I can test to (help) debug this? >> It happens a lot when my machine is under load. (100% CPU) >> Is it possible that it happens since I upgraded the memory from 1GB to 2 >> GB? > > 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? > > Jack I see these too when installing packages over nfs on my Laptop. If I run with a low level of network traffic, i.e. ssh compile, and peg out the cpu with a benchmark such as flops, I don't see these timeouts. 6.1-STABLE FreeBSD 6.1-STABLE #0: Sat Aug 26 14:45:40 CDT 2006 em0@pci2:1:0: class=0x020000 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' class = network Any suggestions? Thanks Dan