From owner-freebsd-isp Mon Jul 20 22:58:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19963 for freebsd-isp-outgoing; Mon, 20 Jul 1998 22:58:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19958 for ; Mon, 20 Jul 1998 22:58:18 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id AAA07859; Tue, 21 Jul 1998 00:57:55 -0500 (CDT) From: Kevin Day Message-Id: <199807210557.AAA07859@home.dragondata.com> Subject: Re: Strange behaviour of ep0 in 2.2.5 In-Reply-To: from Andrew Webster at "Jul 21, 98 00:11:07 am" To: andrew@pubnix.net Date: Tue, 21 Jul 1998 00:57:54 -0500 (CDT) Cc: freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ok before you guys say upgrade, here's the scoop. > > 2.2.5-Stable running as a news server with full feed on a T1 line. > After 80 days, the interface (ep0) went down, ifconfig ep0 down; ifconfig > ep0 up broght the system back to life. > Again at 112 days, same thing. > Yep, the 'ep' driver is definately buggy. :) You'll see things such as: 1) Load average getting higher and higher, while user cpu % getting smaller. 2) Connections randomly getting stuck 3) The card randomly dying, like what you saw ifconfig ep0 down ; ifconfig ep0 up fixes the problem in most cases. Until they can work around the bug, you can go to most big computer stores and get a de0 compatible NetGear FA310TX card for $29.95 (100MB full duplex) I'm still phasing my ep cards out.. the performance difference is astonishing. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message