[nfe] DHCP failure on 8-stable

YongHyeon PYUN pyunyh at gmail.com
Tue Apr 3 02:35:34 UTC 2012


On Mon, Apr 02, 2012 at 07:36:36PM -0400, enoch wrote:
> YongHyeon PYUN <pyunyh at gmail.com> writes:
> 
> > On Mon, Apr 02, 2012 at 03:50:02AM -0400, enoch wrote:
> >> On 04/02/2012 03:52 PM, YongHyeon PYUN wrote:
> >> > 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?
> >> > 
> >> 
> >> Static IP direct communication attempt from this desktop to another
> >> laptop through a crossover cable fails as follows. Thanks.
> >> 
> >> 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 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
> >>         media: Ethernet autoselect (1000baseT
> >> <full-duplex,flowcontrol,master,rxpause,txpause>)
> >>         status: active
> >> 
> >> nfe0: link state changed to UP
> >> nfe0: <NVIDIA nForce 430 MCP13 Networking Adapter> port 0xf200-0xf207
> >> mem 0xefffb000-0xefffbfff irq 21 at device 20.0 on pci0
> >> miibus1: <MII bus> on nfe0
> >
> > It seems you've omitted PHY driver here. What PHY driver was
> > attached to nfe(4)?
> >
> 
> miibus1: <MII bus> on nfe0
> rgephy1: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus1
> 
> >> nfe0: Ethernet address: 00:1f:bc:00:19:dc
> >> nfe0: [FILTER]
> >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
> >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
> >> nfe0: link state changed to UP
> >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
> >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
> >> nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)
> >> 
> >> dev.nfe.0.stats.rx.frame_errors: 0
> >> dev.nfe.0.stats.rx.extra_bytes: 0
> >> dev.nfe.0.stats.rx.late_cols: 0
> >> dev.nfe.0.stats.rx.runts: 0
> >> dev.nfe.0.stats.rx.jumbos: 0
> >> dev.nfe.0.stats.rx.fifo_overuns: 0
> >> dev.nfe.0.stats.rx.crc_errors: 0
> >> dev.nfe.0.stats.rx.fae: 0
> >> dev.nfe.0.stats.rx.len_errors: 0
> >> dev.nfe.0.stats.rx.unicast: 56
> >> dev.nfe.0.stats.rx.multicast: 0
> >> dev.nfe.0.stats.rx.broadcast: 280
> >> dev.nfe.0.stats.tx.octets: 7517
> >> dev.nfe.0.stats.tx.zero_rexmits: 51
> >> dev.nfe.0.stats.tx.one_rexmits: 0
> >> dev.nfe.0.stats.tx.multi_rexmits: 0
> >> dev.nfe.0.stats.tx.late_cols: 0
> >> dev.nfe.0.stats.tx.fifo_underuns: 0
> >> dev.nfe.0.stats.tx.carrier_losts: 0
> >> dev.nfe.0.stats.tx.excess_deferrals: 0
> >> dev.nfe.0.stats.tx.retry_errors: 0
> >> 
> >
> > Thanks. Would you show me the output of "pciconf -lcbv"?
> >
> 
> nfe0 at pci0:0:20:0:       class=0x068000 card=0x10003842 chip=0x026910de rev=0xa3 hdr=0x00
>     vendor     = 'NVIDIA Corporation'
>     device     = 'MCP51 Network Bus Enumerator'
>     class      = bridge
>     bar   [10] = type Memory, range 32, base 0xefffb000, size 4096, enabled
>     bar   [14] = type I/O Port, range 32, base 0xf200, size  8, enabled
>     cap 01[44] = powerspec 2  supports D0 D1 D2 D3  current D0
> 
> Interestingly, now that nfe0 is using a static IP it sometimes boots
> up properly. Are you interested in its good working?

Yes I am. Would you try attached patch and let me know whether the
patch makes any difference on your box?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfe.power.diff
Type: text/x-diff
Size: 954 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20120403/e6f5d076/nfe.power.bin


More information about the freebsd-net mailing list