From owner-freebsd-bugs Mon Jun 16 18:10:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13008 for bugs-outgoing; Mon, 16 Jun 1997 18:10:06 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA12999; Mon, 16 Jun 1997 18:10:02 -0700 (PDT) Resent-Date: Mon, 16 Jun 1997 18:10:02 -0700 (PDT) Resent-Message-Id: <199706170110.SAA12999@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, root@blip.cetlink.net Received: from blip.cetlink.net (blip.cetlink.net [209.54.62.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA12840 for ; Mon, 16 Jun 1997 18:07:44 -0700 (PDT) Received: (from root@localhost) by blip.cetlink.net (8.8.5/8.8.5) id VAA00867; Mon, 16 Jun 1997 21:07:07 -0400 (EDT) Message-Id: <199706170107.VAA00867@blip.cetlink.net> Date: Mon, 16 Jun 1997 21:07:07 -0400 (EDT) From: Charlie Root Reply-To: root@blip.cetlink.net To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: kern/3887: fxp problems Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 3887 >Category: kern >Synopsis: fxp driver looses packets >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 16 18:10:01 PDT 1997 >Last-Modified: >Originator: Jeff Wheat >Organization: Computer Enhancement Technologies, Inc >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: Server: CPU: P5 166MHz Memory: 64MB DRAM Ethernet Card: Intel EtherExpress 10/100B IDE Hard Drive: Western Digital 2.1Gb This ethernet card has 68 aliases bound to it. >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. >Audit-Trail: >Unformatted: