From owner-cvs-src@FreeBSD.ORG Thu Mar 20 02:13:07 2008 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FDBD106566B for ; Thu, 20 Mar 2008 02:13:07 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 2038B8FC18 for ; Thu, 20 Mar 2008 02:13:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so719156wfa.7 for ; Wed, 19 Mar 2008 19:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=UpzpwUAugbxZtGafAvfexlT9ojYHv7m6vhtWY9Igy+k=; b=sdyxmG4wLCuF+HrlVLTtkKMLZy/o9QHZgzwjhRldlFD5dLDGUpBpHDK9YlkzEhwwv/izK6BfDXKUVI16lV1nwaJQZZhsT/qE52xP7bO9p0gQL9aRrqfTy8kgWk/DZeSpiRAsZtEojDlvB+jvhD+I1Ohq6jHBSmhHgn12a+dW9/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=XSF+sgnnNhdWmehC323H5fSmPrZ7LlZsRqddInh5EZDPk7yP2kE6a63j3Pv4I+eLWDBkaHKGITKJ1tQySySmMexohdgCY174cLxtrC0HqoVrHE+a/EYVTfadi/BKQWNnTrVc/5JqP+ObylNLLtYDSs/dA6IXRqLPjYQZ1sk9jxA= Received: by 10.142.231.7 with SMTP id d7mr796610wfh.130.1205977659865; Wed, 19 Mar 2008 18:47:39 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 28sm2085741wfg.17.2008.03.19.18.47.36 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Mar 2008 18:47:38 -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 m2K1lXQn067009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Mar 2008 10:47:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m2K1lWaC067008; Thu, 20 Mar 2008 10:47:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 20 Mar 2008 10:47:32 +0900 From: Pyun YongHyeon To: Sameh Ghane Message-ID: <20080320014732.GF66694@cdnetworks.co.kr> References: <200803110451.m2B4pMLB095467@repoman.freebsd.org> <20080319160534.GD2267@anthologeek.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080319160534.GD2267@anthologeek.net> User-Agent: Mutt/1.4.2.1i Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Pyun YongHyeon Subject: Re: cvs commit: src/sys/dev/vr if_vr.c if_vrreg.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2008 02:13:07 -0000 On Wed, Mar 19, 2008 at 05:05:34PM +0100, Sameh Ghane wrote: > Le (On) Tue, Mar 11, 2008 at 04:51:22AM +0000, Pyun YongHyeon ecrivit (wrote): > > yongari 2008-03-11 04:51:22 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/dev/vr if_vr.c if_vrreg.h > > Log: > A LOT. > > Hi, > > Is this a candidate for MFC ? > > I get a lot of errors on a 7-stable kernel, but not sure if they're really > hardware or kernel related: I think it may not be related with hardware. > kernel: vr0: rx packet lost > kernel: vr0: rx packet lost > kernel: vr0: rx packet lost > kernel: vr0: rx packet lost > kernel: vr0: rx packet lost > kernel: vr0: watchdog timeout > kernel: vr0: Using force reset command. > kernel: vr0: rx packet lost > kernel: vr0: rx packet lost > > > I still hope this commit might help, though I don't have this problem on a > different server, using an 8-current kernel from before your commit. > Normally, it should not be a problem if you don't see too many of dropped packets. These dropping of packets can come from various reasons such as Rx FIFO overrun, bad CRC, duplex/speed mismatch, out of receive descriptors etc. But I guess the other errors such as watchdog timeouts or force reset messages indicate the hardware is in stuck condition. Previously vr(4) lacked proper handling of link state changes as well as reliable error recovery. I think I've fixed most of them. If you can still see these errors it should be fixed in vr(4). You can see these errors with 'dev.vr.0.stats' sysctl on CURRENT. > > And both cards really look the same :) > > vr0: port 0xd800-0xd8ff mem > 0xfaefbc00-0xfaefbcff irq 23 at device 18.0 on pci0 > > vr0: port 0xe000-0xe0ff mem > 0xfbfff800-0xfbfff8ff irq 23 at device 18.0 on pci0 > > > > The good thing is that I might be losing packets, but it still works ! > Yes it should. Dropping packets may severely decrease network performance and reliability though. -- Regards, Pyun YongHyeon