nfe busted on 7.0-BETA4
Rudy
crapsh at monkeybrains.net
Mon Dec 3 21:48:12 PST 2007
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.... here
is the tail of /var/log/messages:
e1000phy0: detached
miibus0: detached
nfe0: detached
nfe0: <NVIDIA nForce 430 MCP13 Networking Adapter> 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: <MII bus> on nfe0
e1000phy0: <Marvell 88E1116 Gigabit PHY> 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?
- Rudy
More information about the freebsd-current
mailing list