From owner-freebsd-stable@FreeBSD.ORG Fri May 9 22:39:44 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 625AC37B408; Fri, 9 May 2003 22:39:44 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2ED443FBF; Fri, 9 May 2003 22:39:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx22-bradley.dialup.earthlink.net ([209.179.198.8] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19EN4l-0001gU-00; Fri, 09 May 2003 22:39:15 -0700 Message-ID: <3EBC9039.3154C20D@mindspring.com> Date: Fri, 09 May 2003 22:38:01 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: vizion communication References: <003701c31668$38371650$15b55042@vizion2000.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46b9f7da6fb1c1b84e83c1e3c29f11df3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: FreeBSD Stable cc: freebsd-smp@freebsd.org Subject: Re: What the???? Is there a Doctor in the house? Help X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 05:39:44 -0000 vizion communication wrote: > Ok do not know what is causing this problem and would > appreciate some help in tracking down the cause. > > FreeBSD 4.7 > > System runs fine for maybe a week and then all networking > stops - without warning. I do not know anyway of persuading > it to resume networking without rebooting. > > Does anyone have some useful suggestions on how to diagnose > the cause? You said you had a XXXX networking card, so that's probably the problem. Try this patch on if_XXXX.c: +XXXXXXXXXX -XXXXXXXXXX (it's a unidiff). 8-) Really, you need to provide us with at last the name of your networking card. Also, you should try to ifconfig down the interface, and then ifconfig it back up, in case it's a lost interrupt or something that needs a timer to correct (doing the ifconfig's will reset the card). -- Terry