From owner-freebsd-current@FreeBSD.ORG Mon Feb 11 13:05:11 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 8CB9916A468 for ; Mon, 11 Feb 2008 13:05:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 48B6913C447 for ; Mon, 11 Feb 2008 13:05:10 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.2/8.14.2) with ESMTP id m1BD5Acs047051; Mon, 11 Feb 2008 08:05:10 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m1BD58ZZ058438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Feb 2008 08:05:09 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200802111305.m1BD58ZZ058438@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 11 Feb 2008 08:03:15 -0500 To: pyunyh@gmail.com From: Mike Tancsa In-Reply-To: <20080211053537.GE2317@cdnetworks.co.kr> References: <20080204022334.GC27999@cdnetworks.co.kr> <200802041545.m14FjpVn014969@lava.sentex.ca> <200802042056.54799.shoesoft@gmx.net> <200802050200.m1520m6m017592@lava.sentex.ca> <20080211053537.GE2317@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: CFT: vr(4) 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: Mon, 11 Feb 2008 13:05:11 -0000 At 12:35 AM 2/11/2008, Pyun YongHyeon wrote: >Sorry for late reply. >I just returned from lunar New Year holiday. Hi, Happy new year :) > > Still seeing some "Forced Reset", although at a slightly lower > > rate. The rx shutdown error is new however. > > > > vr0: vr_stop: Rx shutdown error > > vr0: vr_stop: Rx shutdown error > >These messages are printed from vr_stop() which is called >to stop the operation of the NIC. By any chance do you perodically >stop and restart the interface? Perhaps something to do with dhclient ? > > vr0: Using force reset command. > > > >This message comes from vr_reset() which is always executed first >in vr_init_locked(). Don't know why soft reset does not work under >certain conditions. Datasheet for Rhine III(VT6105M, VT6105LOM) >says nothing about it. I guess you can ignore it unless this >message and above messages are continuously printed on your >console. It doesnt seem to happen too much on releng7. I have been running your driver from the download page for almost a week and it happens a lot less than it does with the RELENG_6 version. I know in RELENG_6, we periodically see the NIC wedge where it doesnt see incoming traffic. Sending out a packet 'wakes it up again' and we see a vr0: Using force reset command. in the logs. Havent see that yet on the modified RELENG_7 version, so so far so good! I will try it on a few more boxes and do some more testing this week. ---Mike