From owner-freebsd-net@FreeBSD.ORG Fri Aug 11 11:42:40 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 BEB8C16A4DE; Fri, 11 Aug 2006 11:42:40 +0000 (UTC) (envelope-from daniel.ryslink@col.cz) Received: from k2.vol.cz (k2.vol.cz [195.250.128.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9D643D66; Fri, 11 Aug 2006 11:42:34 +0000 (GMT) (envelope-from daniel.ryslink@col.cz) Received: from k2.vol.cz (k2.vol.cz [195.250.128.82]) by k2.vol.cz (8.12.11/8.12.9) with ESMTP id k7BBgWtI080992; Fri, 11 Aug 2006 13:42:32 +0200 (CEST) (envelope-from daniel.ryslink@col.cz) Date: Fri, 11 Aug 2006 13:42:32 +0200 (CEST) From: Daniel Ryslink X-X-Sender: kamamura@k2.vol.cz To: Gleb Smirnoff In-Reply-To: <20060811111240.GD96644@FreeBSD.org> Message-ID: <20060811133531.D80282@k2.vol.cz> References: <20060811100536.V80282@k2.vol.cz> <20060811111240.GD96644@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SpamTest-Info: Profile: Formal (493/060809) X-SpamTest-Info: Profile: Detect Standard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking Spam - Subject (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0125], KAS/Release Cc: freebsd-net@FreeBSD.org 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 11:42:40 -0000 Hello, We have started to use the em driver only recently, after the upgrade to gigabit connectivity (100 MBit NICs from Intel used the fxp driver). As for the frequency of the incidents, here is a grep of the messages: ~~~~~~~~~~~~ ~~~~~~~~~~~~~~ Aug 4 22:35:23 b2 kernel: em0: watchdog timeout -- resetting Aug 5 00:09:20 b2 kernel: em1: watchdog timeout -- resetting Aug 5 06:08:59 b2 kernel: em1: watchdog timeout -- resetting Aug 6 12:38:16 b2 kernel: em1: watchdog timeout -- resetting Aug 6 20:39:47 b2 kernel: em0: watchdog timeout -- resetting Aug 7 18:37:29 b2 kernel: em1: watchdog timeout -- resetting Aug 8 07:27:48 b2 kernel: em0: watchdog timeout -- resetting Aug 8 09:38:17 b2 kernel: em0: watchdog timeout -- resetting Aug 8 12:54:54 b2 kernel: em1: watchdog timeout -- resetting Aug 8 22:41:17 b2 kernel: em1: watchdog timeout -- resetting Aug 9 05:17:24 b2 kernel: em1: watchdog timeout -- resetting Aug 9 10:56:10 b2 kernel: em1: watchdog timeout -- resetting Aug 9 20:10:06 b2 kernel: em1: watchdog timeout -- resetting Aug 11 08:41:44 b2 kernel: em0: watchdog timeout -- resetting Aug 11 10:35:43 b2 kernel: em0: watchdog timeout -- resetting ~~~~~~~~~~~~ ~~~~~~~~~~~~~~ The driver used is version 3.2.18 (I wanted to use the Intel 6.1.4 as a module, but I have found out that I made a mistake and accidentally loaded the old 3.2.18 driver). I have dilemma now - which new driver to try? The 6.0.5 submitted to the current FreeBSD 6.1 branch (modified by you, I believe, on 8th August), or the newest driver from Intel 6.1.4? Do you think one of these drivers could solve my problems? I would be very thankful for any advice. Thank you Best Regards Daniel Ryslink On Fri, 11 Aug 2006, Gleb Smirnoff wrote: > Daniel, > > On Fri, Aug 11, 2006 at 10:06:00AM +0200, Daniel Ryslink wrote: > D> We have currently upgraded one of our routers to Gigabit connectivity and > D> FreeBSD 6.1 Release. > D> > D> The hardware is Supermicro SuperServer 5015M-T - we have tried both the > D> integrated NIC and yet another external Intel NIC - specifically > D> > D> Intel PRO/1000 MT Dual Port Server Adapter > D> PWLA8492MT > D> > D> The problem is that several times a day, the following appears in > D> messages: > D> > D> Aug 11 08:41:44 b2 kernel: em0: watchdog timeout -- resetting > D> > D> accompanied with a loss of connectivity lasting for several seconds. > D> > D> We have tried using both the default driver that came with the FreeBSD > D> installation as well as the newest driver from Intel dated 2th April 2006 > D> compiled as a module, but the problem still persists. > D> > D> If anyone encountered the problem and has a solution, I would be very > D> grateful. > > Sometime ago this message was not printed, but the reset was processed > and the loss of connectivity was also present. So, probably you hadn't > noticed this problem before. > > How many times per day is this message printed? > > -- > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE >