From owner-freebsd-stable@FreeBSD.ORG Sun May 26 11:38:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 650EEEB5; Sun, 26 May 2013 11:38:50 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by mx1.freebsd.org (Postfix) with ESMTP id 30F672E5; Sun, 26 May 2013 11:38:49 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id 10so5668511pdi.31 for ; Sun, 26 May 2013 04:38:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=i4uAv6OGVo1xDTtQsKVv1UF/kIwj5jqGCVcZJ3JPIBU=; b=M0bqYMsdqc2D+6+v+OjD2EB0zKxyNOZRAdNed15+2ivUsXvuxjxKPzcOsy/DtnHaJA /lrYWgF3cWQD20sB9gMvR6jypOJIaTaeEu5v5htM92JgCa4NvgcJRaElCZQI9okCQeH1 9BXEX4zNveN2jTAbwrioQ8QI9EkVQ1wLGPOxuOorZ51eQTNpMNGiwBR6G26q0Pdbgvgr xL/Mq4VgKNKq4yplkugiTBLD4JO9+b9aQBHjnipyVy3dWMTsotLXo9Va0YveXO2FcuOj oWzEGISSIg73A84ubtKLu4otjbI4ePBkYD7z6G66mMOGjKBsEdTk8UoMpCVpI/nrmR16 Qo0A== X-Received: by 10.66.139.198 with SMTP id ra6mr25570334pab.140.1369568328482; Sun, 26 May 2013 04:38:48 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id zt1sm7139544pbb.15.2013.05.26.04.38.44 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 26 May 2013 04:38:47 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 26 May 2013 20:38:41 +0900 From: YongHyeon PYUN Date: Sun, 26 May 2013 20:38:41 +0900 To: Hiroki Sato Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130526113841.GA1511@michelle.cdnetworks.com> References: <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> <20130524.163646.628115045676432731.hrs@allbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524.163646.628115045676432731.hrs@allbsd.org> User-Agent: Mutt/1.4.2.3i Cc: jdc@koitsu.org, gjb@freebsd.org, freebsd-stable@freebsd.org, re@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2013 11:38:50 -0000 On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote: > Hiroki Sato wrote > in <20130524.162926.395058052118975996.hrs@allbsd.org>: > > hr> YongHyeon PYUN wrote > hr> in <20130524054720.GA1496@michelle.cdnetworks.com>: > hr> > hr> A workaround is specifying the following line in rc.conf: > hr> > hr> ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex" > > Hmm, I guess this can happen on other NICs when the link negotiation > causes a link-state flap. Is it true? Probably not. AFAIK fxp(4) is the only controller that requires two full resets to support flow control. Multicast programming for fxp(4) also requires full controller reset so trying to renew its existing lease for fxp(4) looks wrong to me. > > -- Hiroki