From owner-freebsd-current@FreeBSD.ORG Mon Mar 3 01:31:54 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 AED811065673 for ; Mon, 3 Mar 2008 01:31:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id 5FE2E8FC22 for ; Mon, 3 Mar 2008 01:31:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so6167835wfa.7 for ; Sun, 02 Mar 2008 17:31:53 -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=8pVQPRei/UP2plnbAKiZ6W5gD5BGfd+GUTaT3UKDuic=; b=Vi4CRx88y1B8DtR8NDx2/e3bP8xrXuluq/PaW08KPWx2NhXZJQjKtQ6oVkM24r9+QJi249Bc+9bitAUEOLm8HbK/g1Su0q2fRdwNX7NS9pxYcYALibjhq8wFHXazLF0oySfEKS0rQ1zL7Gr8wpIrUOnd5I0aBuQfRaRTsyfYTfI= 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=QY2bC+5IAWGRq40RIZdo0Epj95kZX7oSvdjgB6ERGbt0xi32fOVKTCMiS/a8okJNkCYphdAinpzkHL4gTtQpRVum6BaFZ5MjRacjmTNhTo1icJ5jbpDN4VT3o3oXVSLQj5buI9RWrC1qANexchd33J7y5h2QTPVKdElGEcnDA8g= Received: by 10.142.131.18 with SMTP id e18mr8648841wfd.207.1204507913658; Sun, 02 Mar 2008 17:31:53 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 30sm25301526wfd.19.2008.03.02.17.31.49 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Mar 2008 17:31:51 -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 m231Vhx2073345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Mar 2008 10:31:43 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m231Vg7p073344; Mon, 3 Mar 2008 10:31:42 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 3 Mar 2008 10:31:42 +0900 From: Pyun YongHyeon To: Mike Tancsa Message-ID: <20080303013142.GE72895@cdnetworks.co.kr> References: <20080217112104.X80805@fledge.watson.org> <200802171458.26951.freebsd-current@dino.sk> <200802171517.26965.freebsd-current@dino.sk> <20080218081801.GB14601@cdnetworks.co.kr> <20080222054356.GE30497@cdnetworks.co.kr> <200802260503.m1Q53Jm3050738@lava.sentex.ca> <20080226053423.GB47750@cdnetworks.co.kr> <200802271712.m1RHC6Rx060293@lava.sentex.ca> <20080228003027.GA56411@cdnetworks.co.kr> <200803011655.m21GtcMU078673@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803011655.m21GtcMU078673@lava.sentex.ca> 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, 03 Mar 2008 01:31:54 -0000 On Sat, Mar 01, 2008 at 11:53:41AM -0500, Mike Tancsa wrote: Sorry for late handling. I wanted to solve Milan Obuch's issue first before committing vr(4). But it seems that it's not easy to fix Milan's issue. :-( > At 07:30 PM 2/27/2008, Pyun YongHyeon wrote: > > >I never thought this kind of testing. It's good to hear vr(4) > >recovers from the abrupt link change events. I guess this also > >indicates the overhauled vr(4) can close lots of PR for vr(4). > > > BTW, any chance of these fixes being backported to RELENG_7 and > RELENG_6 ? Its not just media speed changes that causes the nic to I'm sure I'll MFC the change to RELENG_7 but not sure it could be done on RELENG_6 due to lack of spare time. > wedge, and up/down transition (eg. a device via xover cable that > reboots) will do the same thing :( Link state change handling includes the following events which could be happend during Tx/Rx operation or idle state against link partner. o link up/down event. o link speed changes. o duplex changes. o flow-control changes(Not activated yet in vr(4)). I guess overhauled vr(4) can handle all above events. > > ---Mike > -- Regards, Pyun YongHyeon