From owner-freebsd-current@FreeBSD.ORG Tue Jun 26 02:24:48 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFC9C16A46B for ; Tue, 26 Jun 2007 02:24:48 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE0A13C44B for ; Tue, 26 Jun 2007 02:24:48 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id l5Q2OiQ5006631; Mon, 25 Jun 2007 19:24:44 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id l5Q2OiYx006630; Mon, 25 Jun 2007 19:24:44 -0700 (PDT) (envelope-from sgk) Date: Mon, 25 Jun 2007 19:24:44 -0700 From: Steve Kargl To: Kevin Gerry Message-ID: <20070626022444.GA6571@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: Re: Issues with 'xl0' keeping link 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: Tue, 26 Jun 2007 02:24:48 -0000 On Mon, Jun 25, 2007 at 06:19:41PM -0700, Kevin Gerry wrote: > I've noticed that after a recent patch, that xl0 is having issues syncing > (Example from log/messages below) and wasn't sure how to 'debug' the > interface to find out what either physically or if the driver is causing it. > (I have attempted replacing the card with the same model) > > /var/log/messages: > Jun 25 18:10:20 storage kernel: xl0: link state changed to DOWN > Jun 25 18:10:22 storage kernel: xl0: link state changed to UP > Jun 25 18:11:30 storage kernel: xl0: link state changed to DOWN > Jun 25 18:11:31 storage kernel: xl0: link state changed to UP > Jun 25 18:12:15 storage kernel: xl0: link state changed to DOWN > Jun 25 18:12:17 storage kernel: xl0: link state changed to UP > Jun 25 18:12:38 storage kernel: xl0: link state changed to DOWN > Jun 25 18:12:39 storage kernel: xl0: link state changed to UP > Good luck in getting any help. bge0 has been going DOWN/UP for about 2 months. I've managed to get around the problem by adding net.inet.tcp.sendspace=131072 net.inet.tcp.recvspace=131072 net.inet.tcp.path_mtu_discovery=0 net.inet.udp.recvspace=65536 net.inet.raw.recvspace=16384 hw.pci.enable_msix=0 hw.pci.enable_msi=0 kern.ipc.nmbclusters=50000 kern.timecounter.hardware=ACPI-fast to /etc/sysctl.conf. I also adjusted a few hardcoded parameters in if_bge.c and if_bgereg.h. -- Steve