From owner-freebsd-net@FreeBSD.ORG Fri Aug 11 16:22:24 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4936116A4DF for ; Fri, 11 Aug 2006 16:22:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF6443D49 for ; Fri, 11 Aug 2006 16:22:22 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id c59so268169pyc for ; Fri, 11 Aug 2006 09:22:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Co7Q02Zrt5XLX28BKZIjEW7wWO2/xop5m27v3CWbXZLaDr+ChHFhzr2VWGlgsfLbxViMnYgLpnWzbFG3TSfuK6ojZ8iFJTh3kgz6zhrOdXbmudMnWG/woseLxrF1Cmvsf5AEE0LBAot6N9TnU4WTQBM0hiDGYvgpiJ5vh47UZ00= Received: by 10.35.111.14 with SMTP id o14mr6423697pym; Fri, 11 Aug 2006 09:22:22 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Fri, 11 Aug 2006 09:22:22 -0700 (PDT) Message-ID: <2a41acea0608110922h4bed63b1ke09f91b610819805@mail.gmail.com> Date: Fri, 11 Aug 2006 09:22:22 -0700 From: "Jack Vogel" To: "Gleb Smirnoff" , "Daniel Ryslink" , freebsd-net@freebsd.org In-Reply-To: <20060811125825.GH96644@cell.sick.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060811100536.V80282@k2.vol.cz> <20060811111240.GD96644@FreeBSD.org> <20060811133531.D80282@k2.vol.cz> <20060811125825.GH96644@cell.sick.ru> Cc: Subject: Re: Problems with em interfaces on FreeBSD 6.1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2006 16:22:24 -0000 On 8/11/06, Gleb Smirnoff wrote: > Daniel, > > On Fri, Aug 11, 2006 at 01:42:32PM +0200, Daniel Ryslink wrote: > D> We have started to use the em driver only recently, after the upgrade to > D> gigabit connectivity (100 MBit NICs from Intel used the fxp driver). > D> > D> As for the frequency of the incidents, here is a grep of the messages: > D> > D> ~~~~~~~~~~~~ ~~~~~~~~~~~~~~ > D> Aug 4 22:35:23 b2 kernel: em0: watchdog timeout -- resetting > D> Aug 5 00:09:20 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 5 06:08:59 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 6 12:38:16 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 6 20:39:47 b2 kernel: em0: watchdog timeout -- resetting > D> Aug 7 18:37:29 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 8 07:27:48 b2 kernel: em0: watchdog timeout -- resetting > D> Aug 8 09:38:17 b2 kernel: em0: watchdog timeout -- resetting > D> Aug 8 12:54:54 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 8 22:41:17 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 9 05:17:24 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 9 10:56:10 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 9 20:10:06 b2 kernel: em1: watchdog timeout -- resetting > D> Aug 11 08:41:44 b2 kernel: em0: watchdog timeout -- resetting > D> Aug 11 10:35:43 b2 kernel: em0: watchdog timeout -- resetting > D> ~~~~~~~~~~~~ ~~~~~~~~~~~~~~ > D> > D> The driver used is version 3.2.18 (I wanted to use the Intel 6.1.4 as a > D> module, but I have found out that I made a mistake and accidentally loaded > D> the old 3.2.18 driver). > D> > D> I have dilemma now - which new driver to try? The 6.0.5 submitted to the > D> current FreeBSD 6.1 branch (modified by you, I believe, on 8th August), or > D> the newest driver from Intel 6.1.4? Do you think one of these drivers > D> could solve my problems? > > I'm not sure whether new driver will solve your problems. You should give > a try to 6.1-STABLE which has 6.0.5 in it. The difference between 6.1.4 and > 6.0.5 is quite small, I doubt that 6.1.4 worth a try in your case. Gleb is right, the difference between my 6.0.5 and 6.1.4 driver are minor and don't seem to have anything to do with your problem. I am happy Gleb got my code merged with tip of STABLE and would take that driver code if I were you, it will become 6.2 before long :) Watchdogs happen because of transmit cleanup failing, your instances are pretty widely seperated, it looks like some external network problem perhaps? Jack Intel LAD