From owner-freebsd-bugs  Mon Jun 16 21:20:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA21783
          for bugs-outgoing; Mon, 16 Jun 1997 21:20:08 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA21747;
          Mon, 16 Jun 1997 21:20:03 -0700 (PDT)
Date: Mon, 16 Jun 1997 21:20:03 -0700 (PDT)
Message-Id: <199706170420.VAA21747@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: David Greenman <dg@root.com>
Subject: Re: kern/3887: fxp problems 
Reply-To: David Greenman <dg@root.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3887; it has been noted by GNATS.

From: David Greenman <dg@root.com>
To: root@blip.cetlink.net
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/3887: fxp problems 
Date: Mon, 16 Jun 1997 21:19:16 -0700

 >>Description:
 >
 >	After running for anywhere from 12 hours to 2 days, the ethernet
 >card becomes unresponsive to any packets. The server continues to operate
 >though attempting to send or receive any packets fails. Netstat -nr shows
 >default route as well as the aliases. Netstat -na shows usually an address
 >bound to port 80 of one of the virtual webservers with a state of LAST_ACK.
 >Rebooting the machine returns all network functions to a normal state.
 >
 >>How-To-Repeat:
 >
 >	Probably sufficient to use an fxp device with multiple aliases
 >bound to the controller. This seems to exist now on two seperate machines.
 >The second machine ran without a single problem until I bound a couple of 
 >aliases. The symtoms are identical to the first server.
 >
 >>Fix:
 >	
 >	Disabling aliases causes the problems to go away.
 
    The problem could be caused by a variety of things. One cause of something
 like this is running out of mbuf clusters. You might get a "Out of mbuf
 clusters - increase maxusers!" message in your /var/log/messages. You can
 increase the maximum number of mbuf clusters with the NMBCLUSTERS kernel
 option (see the mailing list archives). Another possible cause of this could
 be a bug in the 82557 NIC; the receiver goes dead when getting garbage on the
 wire. If you can "ifconfig fxp0 dowm; ifconfig fxp0 up" to clear the problem,
 then this might be the cause. Let me know if you determine anything further
 on this problem.
 
 -DG
 
 David Greenman
 Core-team/Principal Architect, The FreeBSD Project