From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 03:24:00 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 22A4E16A403 for ; Thu, 14 Sep 2006 03:24:00 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB0B943D45 for ; Thu, 14 Sep 2006 03:23:59 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so3143549pye for ; Wed, 13 Sep 2006 20:23:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l+Xpf1xkAow6yqIqe1iDRyYbQJeoYJXSil0Z/yiMZSjdhU7/ATbrsfBS0ZTPe4MSs8K8ERB4q2KhuqopxLhRLAFQnNAaGiOglpZeUfkucKRwuoK8LPxe5+cYs0ezNwJjgHcxIqCb8APHf8WwY9nM6Dyt/KZwccdlF+SGjiqxuIM= Received: by 10.35.96.7 with SMTP id y7mr14207318pyl; Wed, 13 Sep 2006 20:23:59 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Wed, 13 Sep 2006 20:23:58 -0700 (PDT) Message-ID: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> Date: Wed, 13 Sep 2006 20:23:58 -0700 From: "Jack Vogel" To: "Ronald Klop" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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 03:24:00 -0000 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