From owner-freebsd-net@FreeBSD.ORG Thu Aug 17 07:52:49 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 67C3816A4DA for ; Thu, 17 Aug 2006 07:52:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id D194C43D4C for ; Thu, 17 Aug 2006 07:52:48 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id c59so690522pyc for ; Thu, 17 Aug 2006 00:52:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=CfCGm7gCxBgtIzWIHMpz8l+Bvw8EcYuXHddCR1yrMdYwVIImrMvA1mD0EK0kOmhjGkebWuBiiSsy21s/JsPjaedQUG5pZ75AqOu4HNE5yQDJWtq8oWZl7jWly8gAC7uwf9Y0sYTjgsUuwVq2edeekNYWV4vVhTL2eYHEFZeSUU0= Received: by 10.35.61.2 with SMTP id o2mr3118800pyk; Thu, 17 Aug 2006 00:52:48 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 20sm548544nzp.2006.08.17.00.52.45; Thu, 17 Aug 2006 00:52:47 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k7H7srYX052427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Aug 2006 16:54:54 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k7H7sq3O052426; Thu, 17 Aug 2006 16:54:52 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 17 Aug 2006 16:54:52 +0900 From: Pyun YongHyeon To: Daniel Ryslink Message-ID: <20060817075452.GK49739@cdnetworks.co.kr> References: <20060811100536.V80282@k2.vol.cz> <20060817043242.GF49739@cdnetworks.co.kr> <20060817094018.P92593@k2.vol.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060817094018.P92593@k2.vol.cz> User-Agent: Mutt/1.4.2.1i 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 Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Aug 2006 07:52:49 -0000 On Thu, Aug 17, 2006 at 09:45:50AM +0200, Daniel Ryslink wrote: > > Hello, > > Thank you very much for your assistance. > > I am happy to report that we have been able to fix this problem. I just > wanted to wait a day or two to be sure that it won't resurface again. > > The last steps we did were: > > 1) Upgrade SuperMicro SS5015M-T BIOS from version 1.1 to version 1.1a > 2) Inclusion of 'debug.mpsafenet=0' into /boot/loader.conf suggested in > this mailing list. > > I would guess that the step 2 was what really solved the problem. > Hmm... I'd like to know whether my patch help or not. Step 2 you mentioned is not the way to go. We're trying very hard to remove giant locks in every places on FreeBSD. > Best Regards > Daniel Ryslink > > On Thu, 17 Aug 2006, Pyun YongHyeon wrote: > > >On Fri, Aug 11, 2006 at 10:06:00AM +0200, Daniel Ryslink wrote: > >> > >> Hello, > >> > >> We have currently upgraded one of our routers to Gigabit connectivity and > >> FreeBSD 6.1 Release. > >> > >> The hardware is Supermicro SuperServer 5015M-T - we have tried both the > >> integrated NIC and yet another external Intel NIC - specifically > >> > >> Intel PRO/1000 MT Dual Port Server Adapter > >> PWLA8492MT > >> > >> The problem is that several times a day, the following appears in > >> messages: > >> > >> Aug 11 08:41:44 b2 kernel: em0: watchdog timeout -- resetting > >> > >> accompanied with a loss of connectivity lasting for several seconds. > >> > >> We have tried using both the default driver that came with the FreeBSD > >> installation as well as the newest driver from Intel dated 2th April 2006 > >> compiled as a module, but the problem still persists. > >> > >> If anyone encountered the problem and has a solution, I would be very > >> grateful. > >> > > > >Because I can't reproduce it here and I failed to find a possible > >cause of the issue. > >As a last resort would you give attached patch a try? > >The patch was generated against latest stable. > > > >-- > >Regards, > >Pyun YongHyeon > > -- Regards, Pyun YongHyeon