From owner-freebsd-current@FreeBSD.ORG Mon Feb 11 05:46:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5877E16A41A for ; Mon, 11 Feb 2008 05:46:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id 20D9413C46A for ; Mon, 11 Feb 2008 05:46:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so150433wfa.7 for ; Sun, 10 Feb 2008 21:46:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=jJJ02RVqxskwWJneL9BJKaEV230FSDeM89f2dD5BvOY=; b=FRenq02IhMRhlL0QBZwtdGBoL5Rtzl0Y3O2srB0tlwXdWRuS5vJEhlwnAqKI4IjZ2O38kwiEZk3XbnxSjAvFvXzkZY4+2UH5PZ1eme9IG8JW0Kn+q1LCGSLPQrhvSf7ConVF1zifNXGGTyLG7s55ppyz7SekXPMNqoTHFn5l2Tg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=LkJSUGkfLVhkkxsIt4G1uwkidYpB146opTVKIU3d/aq1JYUmVRayAHLMxaqH94aB+8APCAYUNrts+5PlbxUeeemtGtszdGtsf3Y83Cx4dB/11roiQUv5UvM/f4w+9oCKNUsuob6UJvDLbLCuVYzBRedv1skjpVZzxTNryqfJFd0= Received: by 10.142.172.12 with SMTP id u12mr8198289wfe.195.1202708802862; Sun, 10 Feb 2008 21:46:42 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 20sm3744411wfi.14.2008.02.10.21.46.40 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Feb 2008 21:46:41 -0800 (PST) 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 m1B5ka8R003697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Feb 2008 14:46:36 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m1B5kanf003696; Mon, 11 Feb 2008 14:46:36 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 11 Feb 2008 14:46:36 +0900 From: Pyun YongHyeon To: Marcin Wisnicki Message-ID: <20080211054636.GG2317@cdnetworks.co.kr> References: <20080204022334.GC27999@cdnetworks.co.kr> <200802041545.m14FjpVn014969@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: CFT: vr(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2008 05:46:43 -0000 On Sun, Feb 10, 2008 at 03:59:16PM +0000, Marcin Wisnicki wrote: > On Mon, 04 Feb 2008 17:47:44 +0000, Marcin Wisnicki wrote: > > > I'm not 100% sure if this is all that is required for RELENG6, but it > > works wonderfully so far. > > > > Even fixed Rx errors I was seeing for some time and didn't have the time > > to investigate whether they were caused by some recent commit to releng6 > > (like the last mfc) or simply a hardware failure. > > > > Thank you Pyun YongHyeon! > > > >>From my dmesg: > > vr0: port 0xd800-0xd8ff mem > > 0xdffefd00-0xdffefdff irq 5 at device 18.0 on pci0 vr0: Quirks: 0x0 > > vr0: Revision: 0x74 > > miibus1: on vr0 > > ukphy0: on miibus1 ukphy0: > > 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet > > address: 42:00:e6:65:9b:11 vr0: [GIANT-LOCKED] > > > > Just noticed in dmesg after reboot: > > vr0: Tx underrun -- increasing Tx threshold(128 -> 256) > vr0: Tx underrun -- increasing Tx threshold(256 -> 512) > vr0: Tx underrun -- increasing Tx threshold(512 -> 1024) > vr0: Tx underrun -- using store and forward mode > vr0: Tx underrun -- > > at this moment I started copying files in and out using samba > and then last message started to repeat for some time with decreasing > frequency until finally: > > vr0: watchdog timeout > > and no more errors were reported. > Due to the poor Tx performance of the hardware, I frequently saw Tx underrun errors on fast machines. The driver automatically attempts to double Tx threshold for each Tx underrun error. It seems that vr(4) still spews Tx underrun errors even with store-and-forward method. If this is the case I have no idea how to fix that. I've not encountered this on CURRENT so it could be related with Giant lock. I'll let you know if I find more clue. > Despite the errors in dmesg everything seems to work fine at all times > with samba tx performance of 9.5mb/s and rx of 8.5mb/s using Vista as a > client. > -- Regards, Pyun YongHyeon