From owner-freebsd-bugs@FreeBSD.ORG  Fri Nov 12 00:00:54 2010
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 9737B1065674;
	Fri, 12 Nov 2010 00:00:54 +0000 (UTC)
	(envelope-from yongari@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 871818FC23;
	Fri, 12 Nov 2010 00:00:54 +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 oAC00sV6079054;
	Fri, 12 Nov 2010 00:00:54 GMT
	(envelope-from yongari@freefall.freebsd.org)
Received: (from yongari@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAC00sG5079043;
	Fri, 12 Nov 2010 00:00:54 GMT (envelope-from yongari)
Date: Fri, 12 Nov 2010 00:00:54 GMT
Message-Id: <201011120000.oAC00sG5079043@freefall.freebsd.org>
To: rfarmer@predatorlabs.net, yongari@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	yongari@FreeBSD.org
From: yongari@FreeBSD.org
Cc: 
Subject: Re: kern/152150: nfe(4) not working on Asus P5N32-SLI Premium
	motherboard (nforce 590)
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 00:00:54 -0000

Synopsis: nfe(4) not working on Asus P5N32-SLI Premium motherboard (nforce 590)

State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Thu Nov 11 23:59:50 UTC 2010
State-Changed-Why: 
It seems you have three issues here.
 o watchdog timeout issue
 o can't send/receive frames with either DHCP and static IP assignment
 o generate bogus traffic storm which in turn make systems connected to
   switch lost connection 

For watchdog timeout issue, would you try the patch at the
following URL?
http://people.freebsd.org/~yongari/nfe/nfe.watchdog.diff

The second issue could be related with tracking of link state
change. The patch above will show "LINK UP" message on your console
if nfe(4) think it established a link. Otherwise it would print
"LINK DOWN". In order to send/receive frames, you always have to
see "LINK UP" message first. Please check whether you can see the
message with DHCP or static IP configuration.

I have no idea for the last issue. Can you see what kind of traffic
is generated on link partner side? I think you can connect two
systems with straight cable and see what kind of traffic does the
nfe(4) generate on other system with tcpdump. If it's 802.3x flow
control traffic I have idea how to keep it from happening.


Responsible-Changed-From-To: freebsd-bugs->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Thu Nov 11 23:59:50 UTC 2010
Responsible-Changed-Why: 
Grab.

http://www.freebsd.org/cgi/query-pr.cgi?pr=152150