From rfg@tristatelogic.com  Sat Jan  1 23:02:51 2011
Return-Path: <rfg@tristatelogic.com>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E09E8106564A
	for <FreeBSD-gnats-submit@freebsd.org>; Sat,  1 Jan 2011 23:02:51 +0000 (UTC)
	(envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118])
	by mx1.freebsd.org (Postfix) with ESMTP id C07258FC0C
	for <FreeBSD-gnats-submit@freebsd.org>; Sat,  1 Jan 2011 23:02:51 +0000 (UTC)
Received: by segfault.tristatelogic.com (Postfix, from userid 1237)
	id 21C75BDC46; Sat,  1 Jan 2011 15:02:51 -0800 (PST)
Message-Id: <20110101230251.21C75BDC46@segfault.tristatelogic.com>
Date: Sat,  1 Jan 2011 15:02:51 -0800 (PST)
From: Ronald F.Guilmette <rfg@tristatelogic.com>
Reply-To: Ronald F.Guilmette <rfg@tristatelogic.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: nfe0 malfunction at boot time
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         153610
>Category:       kern
>Synopsis:       [nfe] nfe0 malfunction at boot time
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 01 23:10:10 UTC 2011
>Closed-Date:    Fri Jun 24 02:04:03 UTC 2011
>Last-Modified:  Fri Jun 24 02:04:03 UTC 2011
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 8.1-RELEASE amd64
>Organization:
Infinite Monkeys & Co.
>Environment:

FreeBSD 8.1-RELEASE amd64

Gigabyte GA-m55plus-S3G nmotherboard w/ Nvidia 430 Southbridge

Onboard Ethernet port hardwired up to a stock Linksys WRT54G wireless
router configured for static (i.e. NO DHCP)

>Description:

Upon boot-up of the GA-m55plus-S3G based system, I get an (unending?)
stream of console/syslog messages exactly like this:

nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)

After googling around awhile, I learned that this is an old, and apparently
still unsolved problem:

  http://kerneltrap.org/mailarchive/freebsd-current/2008/1/18/578972

The thread above suggested that I try manually down-ing and then up-ing
the nfe0 interface.  I did that, and yes, that causes the problem to go
away and after that up/down the interface seems to be functioning normally.
However this server SHOULD be able to recover gracefully from, e.g.,
power failures, even when I am out of town, so what am I supposed to do?
Should I add "manual" down & up commands for this interface to my
/etc/rc.local file??

Ideally, I shouldn't have to do that (and I'm not even 100% sure that even
doing that will produce reliable results).

>How-To-Repeat:

See above.  Get yourself a motherboard with an Nvidia 430 Southbridge
on it, and then wire up the ethernet port from that to a stock Linksys
WRT54G, set the Linksys box to NO DHCP (although that probably doesn't
matter), give the nfe0 device a static IP in your /etc/rc.conf file
(although that probably doesn't matter either), and then do a cold restart.

>Fix:

Beats me.  I am forced to workaround this for now by installing a cheapie
Realtek ethernet card (which most certainly works).

That's a pity, because I wanted to try using the gigabit capability of the
onboard Nvidia ethernet port.  Oh well.  I'll live.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Jan 3 19:07:07 UTC 2011 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=153610 
Responsible-Changed-From-To: freebsd-net->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Thu Jan 20 21:45:36 UTC 2011 
Responsible-Changed-Why:  
Grab. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=153610 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Thu Jan 20 22:04:38 UTC 2011 
State-Changed-Why:  
Show me the output of dmesg and "ifconfig nfe0" after seeing 
"nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0)" 
message. 
Also include the output of "sysctl dev.nfe.0.stats". 

http://www.freebsd.org/cgi/query-pr.cgi?pr=153610 
State-Changed-From-To: feedback->closed 
State-Changed-By: yongari 
State-Changed-When: Fri Jun 24 02:03:05 UTC 2011 
State-Changed-Why:  
Close, feedback timeout(> 5 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=153610 
>Unformatted:
