Apparent fxp regression in FreeBSD 8.4-RC3

[YongHyeon PYUN]

On Fri, May 24, 2013 at 03:32:29AM -0400, Charles Sprickman wrote:
> 
> On May 24, 2013, at 1:47 AM, 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 have a system up and running and showing the problem (that was
> non-trival, just for the record - one machine blew the PSU after
> POST, the other refused to boot off an IDE drive, and then required
> two CD-ROM drives before I found a functional one, and it took a
> good half-hour to find what's apparently the last piece of writable
> CD-R media I own).
> 
> I am not awesome with svn, but I'll see if I can manually undo
> r247336 and give it a spin.

Download
http://svnweb.freebsd.org/base/stable/8/sbin/dhclient/dhclient.c?r1=231278&r2=247336&view=patch

And apply the patch with -R.