From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 23:10:11 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4A62106567A for ; Sat, 1 Jan 2011 23:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA628FC15 for ; Sat, 1 Jan 2011 23:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01NAAS7059059 for ; Sat, 1 Jan 2011 23:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01NAA3J059058; Sat, 1 Jan 2011 23:10:10 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 23:10:10 GMT Resent-Message-Id: <201101012310.p01NAA3J059058@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Ronald F.Guilmette" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E09E8106564A for ; 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 ; 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" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: kern/153610: nfe0 malfunction at boot time X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ronald F.Guilmette" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 23:10:11 -0000 >Number: 153610 >Category: kern >Synopsis: nfe0 malfunction at boot time >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 23:10:10 UTC 2011 >Closed-Date: >Last-Modified: >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: >Unformatted: