From owner-freebsd-stable@FreeBSD.ORG  Fri May 24 07:52:39 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 865CD975;
 Fri, 24 May 2013 07:52:39 +0000 (UTC)
 (envelope-from john@theusgroup.com)
Received: from theusgroup.com (theusgroup.com [64.122.243.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 68EC3405;
 Fri, 24 May 2013 07:52:39 +0000 (UTC)
From: John <john@theusgroup.com>
To: Hiroki Sato <hrs@FreeBSD.org>
Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3
In-reply-to: <20130524.162926.395058052118975996.hrs@allbsd.org>
References: <20130524044035.GA40957@icarus.home.lan>
 <20130524044919.GA41292@icarus.home.lan>
 <20130524054720.GA1496@michelle.cdnetworks.com>
 <20130524.162926.395058052118975996.hrs@allbsd.org>
Comments: In-reply-to Hiroki Sato <hrs@FreeBSD.org>
 message dated "Fri, 24 May 2013 16:29:26 +0900."
Date: Fri, 24 May 2013 00:46:45 -0700
Message-Id: <20130524074645.22C52A30@server.theusgroup.com>
Cc: pyunyh@gmail.com, jdc@koitsu.org, freebsd-stable@FreeBSD.org,
 re@FreeBSD.org, gjb@FreeBSD.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 07:52:39 -0000

>YongHyeon PYUN <pyunyh@gmail.com> wrote
>  in <20130524054720.GA1496@michelle.cdnetworks.com>:
>
>py> On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
>py> > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
>py> > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
>py> > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
>py> > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can
>py> > > > > do so with both NICs), just let me know; it should only take me half an
>py> > > > > hour or so.
>py> > > > >
>py> > > > > I'll politely wait for someone to say "please do so" else won't bother.
>py> > > > >
>py> > > >
>py> > > > For the sake of completeness...
>py> > > >
>py> > > > "Please do so."  :)
>py> > >
>py> > > Issue reproduced 100% reliably, even within sysinstall.
>py> > >
>py> > > {snip}
>py> >
>py> > Forgot to add:
>py> >
>py> > This issue ONLY happens when using DHCP.
>py> >
>py> > Statically assigning the IP address works fine; fxp0 goes down once,
>py> > up once, then stays up indefinitely.
>py>
>py> I asked Mike to try backing out dhclient(8) change(r247336) but it
>py> seems he missed that. Jeremy, could you try that?
>py>
>py> I guess dhclient(8) does not like flow-control negotiation of
>py> fxp(4) after link establishment.
>
> Okay, I could reproduce this issue on my box.  After invocation of
> dhclient(8), a link is up and then state_reboot() drops the link
> establishment.  Removing the changes around RTM_IFINFO in r247336
> makes it work with no problem.
>
> A workaround is specifying the following line in rc.conf:
>
> ifconfig_fxp0="DHCP media 100baseTX mediaopt full-duplex"
>
>-- Hiroki

I can confirm that backing out r247336 on a box running 9.1-stable.r250229
fixes the problem. I hadn't seen the problem before because the box normally
has a static ip address.

John Theus
TheUsGroup.com