Date: Mon, 02 Apr 2012 19:36:36 -0400 From: enoch <ixew@hotmail.com> To: freebsd-net@freebsd.org Subject: Re: [nfe] DHCP failure on 8-stable Message-ID: <87ty11670b.fsf@hotmail.com> References: <jl3lp1$lla$1@dough.gmane.org> <20120330233819.GC7325@michelle.cdnetworks.com> <4F75C5EC.6090303@hotmail.com> <20120402195215.GA3571@michelle.cdnetworks.com> <jlblna$ptp$1@dough.gmane.org> <20120403023225.GD3571@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
YongHyeon PYUN <pyunyh@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@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?
Thanks, Enoch.
>> >>
>> >> 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@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
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ty11670b.fsf>