From owner-freebsd-questions Mon Sep 2 11:45:18 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA2E437B400 for ; Mon, 2 Sep 2002 11:45:14 -0700 (PDT) Received: from infinity.aesredfish.net (ns1.aesredfish.net [65.168.0.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id D128243E42 for ; Mon, 2 Sep 2002 11:45:13 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (mhope-dhcp-65-168-1-181.dashfast.com [65.168.1.181]) by infinity.aesredfish.net (8.11.6/8.11.0) with ESMTP id g82IihD22928; Mon, 2 Sep 2002 14:44:44 -0400 Message-ID: <3D73B350.50209@potentialtech.com> Date: Mon, 02 Sep 2002 14:52:00 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020502 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Patrick O'Reilly" Cc: Warren Block , FreeBSD Question List Subject: Re: Network Communications stopped for no apparent reason?!? References: <006101c252af$7c1fabc0$0200000a@perimeter.co.za> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Patrick O'Reilly wrote: > From: "Warren Block" > >>>I have experienced something very strange today. A server >>>running 4.6.2 just stopped talking to the network. I cannot >>>find any clues as to why! >> >>Others have experienced this and it's been discussed on the >>-stable mailing list. Don't know if the cause is known or >>there's a solution yet, though. Look for the thread called >>"network lockups". > > > Warren, > > thanks for the pointer. Unfortunately there was nothing in the way of a > solution there :( > > Anyone else? I am still mystified by this one. You've snipped a considerable amount of your previous message, so if I'm remembering wrong, forgive me. I seem to remember that you were getting TX problems with a dc interface? If memeroy serves, many of the cards that use the dc driver are problematic. If you have the resources, try a different NIC. I could be way off base on this ... I hope it's not a wild goose chase. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message