From nobody@FreeBSD.org  Sun Jun 19 18:32:38 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BBB7316A41C
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 19 Jun 2005 18:32:38 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A71E843D49
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 19 Jun 2005 18:32:38 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j5JIWcQW084804
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 19 Jun 2005 18:32:38 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j5JIWc0V084803;
	Sun, 19 Jun 2005 18:32:38 GMT
	(envelope-from nobody)
Message-Id: <200506191832.j5JIWc0V084803@www.freebsd.org>
Date: Sun, 19 Jun 2005 18:32:38 GMT
From: Christian <christian@karg.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: fxp0: device timeout, fxp interface dies on 5.4/amd64/smp under load
X-Send-Pr-Version: www-2.3

>Number:         82425
>Category:       amd64
>Synopsis:       [fxp] fxp0: device timeout, fxp interface dies on 5.4/amd64/smp under load
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gavin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 19 18:40:18 GMT 2005
>Closed-Date:    Sat Jan 26 19:27:45 UTC 2008
>Last-Modified:  Sat Jan 26 19:27:45 UTC 2008
>Originator:     Christian
>Release:        FreeBSD 5.4-STABLE
>Organization:
>Environment:
FreeBSD nox.internal.net 5.4-STABLE FreeBSD 5.4-STABLE #2: Sat Jun 18 22:29:48 BST 2005     root@nox.internal.net:/usr/obj/usr/src/sys/NOX  amd64

>Description:
With the machine operating as a server under greater than moderate network
traffic load, the fxp interface becomes dysfunctional, printing a message
"fxp0: device timeout" on the console. While fxp0 is still marked 'up' as
per ifconfig, it doesn't tx/rx any traffic at all. The machine also no
longer responds to external pings.

The problem machine is a dual-Opteron system, running an SMP kernel.
>How-To-Repeat:
option 1: using the rsync port. Using a second machine, attempt to perform
a large rsync to the problem machine. Attempting to send a Maildir mail
folder hierarchy with about 318MB in about 36000 files causes fxp0 on the
problem machine to die, sometimes only a few dozen files into the rsync.

option 2: using nfs. Setup the problem machine as an nfs server, and
attempt to copy the above mail directory to the nfs share on the problem
machine. fxp0 on the problem machine will die with "fxp0: device timeout".
>Fix:
no fix known, rebooting the problem machine brings fxp0 back to life.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: gavin 
State-Changed-When: Sun Sep 16 17:04:13 UTC 2007 
State-Changed-Why:  
To submitter:  Does this still occur on more recent versions of 
FreeBSD? 


Responsible-Changed-From-To: freebsd-amd64->gavin 
Responsible-Changed-By: gavin 
Responsible-Changed-When: Sun Sep 16 17:04:13 UTC 2007 
Responsible-Changed-Why:  
Take 

http://www.freebsd.org/cgi/query-pr.cgi?pr=82425 
State-Changed-From-To: feedback->closed 
State-Changed-By: gavin 
State-Changed-When: Sat Jan 26 19:26:28 UTC 2008 
State-Changed-Why:  
Feedback timeout (3 months), not enough info to diagnose further  
without feedback. 

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