Date: Thu, 23 May 2013 22:58:32 -0700 From: Jeremy Chadwick <jdc@koitsu.org> To: YongHyeon PYUN <pyunyh@gmail.com> Cc: Glen Barber <gjb@freebsd.org>, freebsd-stable@freebsd.org, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524055832.GA42673@icarus.home.lan> In-Reply-To: <20130524054720.GA1496@michelle.cdnetworks.com> References: <alpine.BSF.2.00.1305232013110.14717@familysquires.net> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 24, 2013 at 02:47:20PM +0900, YongHyeon PYUN wrote:
> On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
> > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
> > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
> > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
> > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can
> > > > > do so with both NICs), just let me know; it should only take me half an
> > > > > hour or so.
> > > > >
> > > > > I'll politely wait for someone to say "please do so" else won't bother.
> > > > >
> > > >
> > > > For the sake of completeness...
> > > >
> > > > "Please do so." :)
> > >
> > > Issue reproduced 100% reliably, even within sysinstall.
> > >
> > > {snip}
> >
> > Forgot to add:
> >
> > This issue ONLY happens when using DHCP.
> >
> > Statically assigning the IP address works fine; fxp0 goes down once,
> > up once, then stays up indefinitely.
>
> I asked Mike to try backing out dhclient(8) change(r247336) but it
> seems he missed that. Jeremy, could you try that?
>
> I guess dhclient(8) does not like flow-control negotiation of
> fxp(4) after link establishment.
I can't test anything without an ISO -- the system in question is truly
"bare-bones" (no hard disk, can't boot USB memsticks, etc.). I'm not a
good test subject for changes on this one, I'm sorry to say. :-(
If there's some way to disable flow-control negotiation in fxp(4) or
miibus(4) via loader, I can try that, but I don't know what the MIB
name would be.
<ignore me, I'm just pissed off>
If r247336 turns out to be the cause: ironic, as r247336 references PR
166656, which was tested against -- wait for it -- xl(4).
People in *this* thread are saying "screw legacy hardware" yet the PR is
for something as old as the 3C905B? Maybe I should bow out of this
thread before I have an aneurysm.
</ignore>
--
| Jeremy Chadwick jdc@koitsu.org |
| UNIX Systems Administrator http://jdc.koitsu.org/ |
| Mountain View, CA, US |
| Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130524055832.GA42673>