[nfe] DHCP failure on 8-stable

[YongHyeon PYUN]

On Fri, Mar 30, 2012 at 10:40:44AM -0400, enoch wrote:
> On 03/30/2012 19:38, YongHyeon PYUN wrote:
> > On Fri, Mar 30, 2012 at 03:01:52AM -0400, enoch wrote:
> >> Recently it became extremely difficult to pass the DHCP discovery step
> >> on boot. Now I am using the buggy [nve] instead.
> >>
> >> Can anyone help?
> >>
> > 
> > Did you set synchronous_dhclient option in rc.conf? 
> > 
> 
> Yes: ifconfig_nfe0="SYNCDHCP"
> 
> I guess [nfe] is undergoing gradual devel changes of some sort as before
> it had some chance of reporting "empty headers" on initial ifconfig and
> refusing to work. Sorry, I should have reported when encountering the
> first problems rather than solve by reboot.

Would you show me the output of both dmesg(nfe(4) and its PHY only)
and 'sysctl dev.nfe.0.stats'?
It would be also helpful to know whether nfe(4) still sees
incoming traffic.
Does assigning static IP work?

> 
> In any case, the alternative [nve] should be marked "dangerous" as under
> heavy load it tends to crash the system.
> 
> Thanks, Enoch.
> 
> >>
> >> uname -a
> >> ~~~~~~~~
> >> FreeBSD dome 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #7: Thu Mar 29
> >> 14:37:00 EDT 2012     root at dome:/usr/obj/usr/src/sys/DOME  amd64
> >>
> >> nfe0 fails at DHCPDISCOVER.
> >>
> >> ifconfig:
> >>
> >> nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >> 	options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>
> >> 	ether 00:1f:bc:00:19:dc
> >> 	inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> >> 	media: Ethernet autoselect (100baseTX <full-duplex>)
> >> 	status: active
> >>
> >> lspci:
> >>
> >> 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)

Because there are several MCP51 variants, "pciconf -lcbv" is more
more preferred one.