From owner-freebsd-current@FreeBSD.ORG Sun Jul 2 17:06:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F4616A417 for ; Sun, 2 Jul 2006 17:06:53 +0000 (UTC) (envelope-from kamtha@mail.ak-labs.net) Received: from ak-labs.net (mail.ak-labs.net [71.140.59.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE224459E for ; Sun, 2 Jul 2006 17:06:39 +0000 (GMT) (envelope-from kamtha@mail.ak-labs.net) Received: from mail.ak-labs.net (localhost [127.0.0.1]) by ak-labs.net (8.13.3/8.13.3) with ESMTP id k62H5DEo021019; Sun, 2 Jul 2006 10:05:14 -0700 (PDT) (envelope-from kamtha@mail.ak-labs.net) Received: (from kamtha@localhost) by mail.ak-labs.net (8.13.3/8.13.3/Submit) id k62H5D1V021018; Sun, 2 Jul 2006 10:05:13 -0700 (PDT) (envelope-from kamtha) Date: Sun, 2 Jul 2006 10:05:13 -0700 From: Carlos Sean Kamtha To: Michiel Boland Message-ID: <20060702170512.GA16009@ak-labs.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:06:53 -0000 On Sun, Jul 02, 2006 at 04:29:27PM +0200, Michiel Boland wrote: > Hi. I frequently get > > em0: watchdog timeout -- resetting > > messages, followed by loss of network at the most inopportune moments. > > It appears that it can be triggered by things like typing 'portinstall > mozilla' over an SSH connection. But that is just a hunch. > > Any ideas how to debug this further? > > Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. > I suggest that this is an hardware issue. I have dealt with this problem before and fixed it by replacing the NIC. I hope this is an option for now. Carlos.