From owner-freebsd-current@FreeBSD.ORG Thu Jul 6 13:41:56 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 D56BB16A4DD; Thu, 6 Jul 2006 13:41:56 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from ms-smtp-04.southeast.rr.com (ms-smtp-04.southeast.rr.com [24.25.9.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BEFD43D70; Thu, 6 Jul 2006 13:41:53 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-04.southeast.rr.com (8.13.6/8.13.6) with ESMTP id k66DfgmJ015760; Thu, 6 Jul 2006 09:41:43 -0400 (EDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.6/8.13.6) with ESMTP id k66DfgpC004532; Thu, 6 Jul 2006 09:41:42 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Thu, 6 Jul 2006 09:41:42 -0400 (EDT) From: Wesley Morgan To: Gleb Smirnoff In-Reply-To: <20060706085358.GA96644@FreeBSD.org> Message-ID: <20060706091811.T977@volatile.chemikals.org> References: <20060702115840.L12091@volatile.chemikals.org> <20060706085358.GA96644@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Michiel Boland , 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: Thu, 06 Jul 2006 13:41:56 -0000 On Thu, 6 Jul 2006, Gleb Smirnoff wrote: > On Sun, Jul 02, 2006 at 12:01:43PM -0400, Wesley Morgan wrote: > W> >Hi. I frequently get > W> > > W> >em0: watchdog timeout -- resetting > W> > > W> >messages, followed by loss of network at the most inopportune moments. > W> > > W> >It appears that it can be triggered by things like typing 'portinstall > W> >mozilla' over an SSH connection. But that is just a hunch. > W> > > W> >Any ideas how to debug this further? > W> > > W> >Hardware is a dell optiplex GX270. Kernel is -CURRENT from 29 june. > W> > W> I have the same issue on my laptop. It seems like the problem came into > W> being a few months ago, but I've never gone any further than trying to > W> revert to a previous version of the driver, which did not help. > > In rev. 1.107 of if_em.c there was a fix that made this message > printed. Before 1.107 the reset was issued, but driver was silent about > this. > > W> For me, the problem is more than just loss of network, but rather every > W> application hanging while multiple timeouts occurr. > > Hmm. May be you are using serial console and system lags when the > console messages are printed? No. I didn't have this laptop until after the 1.107 commit, either. It was probably always doing the timeout, I just never used it much until more recently. -- This .signature sanitized for your protection