Date: Sun, 26 May 2013 20:38:41 +0900 From: YongHyeon PYUN <pyunyh@gmail.com> To: Hiroki Sato <hrs@freebsd.org> Cc: jdc@koitsu.org, gjb@freebsd.org, freebsd-stable@freebsd.org, re@freebsd.org Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130526113841.GA1511@michelle.cdnetworks.com> In-Reply-To: <20130524.163646.628115045676432731.hrs@allbsd.org> References: <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> <20130524.163646.628115045676432731.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote: > Hiroki Sato <hrs@FreeBSD.org> wrote > in <20130524.162926.395058052118975996.hrs@allbsd.org>: > > hr> YongHyeon PYUN <pyunyh@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130526113841.GA1511>