On Mon, Dec 03, 2007 at 09:48:45PM -0800, Rudy wrote:
>
> Still Lots of these at boot...
>
> 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)
> 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)
> 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)
> 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)
> 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)
>
> I compiled the nfe as a MODULE so I could kldunload it and load up the nve
> -- if the patch didn't work. So, I added if_nfe_load to my
> /boot/loader.conf. Following my plan, I ran kldunload if_nfe... BUT! the
> module was automatically reloaded AND started to work properly. Hmmm....


It's confusing. Does it mean the patch fixed the issue?
Are you sure the nfe(4) kernel module used at boot is patched nfe(4)?

> here is the tail of /var/log/messages:
>
> e1000phy0: detached
> miibus0: detached
> nfe0: detached
> nfe0: port 0xc800-0xc807 mem
> 0xfe02b000-0xfe02bfff irq 22 at device 20.0 on pci0
> nfe0: Ethernet address: 00:17:31:be:4c:2f
> nfe0: [FILTER]
> miibus0: on nfe0
> e1000phy0: PHY 1 on miibus0
> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
> auto
> nfe0: link state changed to DOWN
> nfe0: link state changed to UP
>
> Is that a bug/feature that the nfe automatically reloads itself?
>


That's odd. In the days of 7-CURRENT I also encountered it but I think
it was fixed as I can't reproduce it. If it still happen, kill devd(8)
and experiment with kldload/kldunload.

> - Rudy


--
Regards,
Pyun YongHyeon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis...reebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"