From owner-freebsd-questions@FreeBSD.ORG Mon Nov 28 16:25:09 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 D32ED16A41F for ; Mon, 28 Nov 2005 16:25:09 +0000 (GMT) (envelope-from dvorakv@vdsoft.org) Received: from mail.vdsoft.org (poseidon.vdsoft.org [193.85.147.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED3443D45 for ; Mon, 28 Nov 2005 16:25:08 +0000 (GMT) (envelope-from dvorakv@vdsoft.org) Received: from [10.0.0.132] (laptop.home.deltaeng.com [10.0.0.132]) by mail.vdsoft.org (Postfix) with ESMTP id BF6FB47E017; Mon, 28 Nov 2005 17:25:00 +0100 (CET) Message-ID: <438B2F66.8050408@vdsoft.org> Date: Mon, 28 Nov 2005 17:25:10 +0100 From: Vladimir Dvorak User-Agent: Debian Thunderbird 1.0.6 (X11/20050802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: danial_thom@yahoo.com References: <20051128155242.6086.qmail@web33312.mail.mud.yahoo.com> In-Reply-To: <20051128155242.6086.qmail@web33312.mail.mud.yahoo.com> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bernhard Fischer , Hans Nieser , freebsd-questions@freebsd.org Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 16:25:09 -0000 Danial Thom wrote: >--- Vladimir Dvorak wrote: > > > >>Bernhard Fischer wrote: >> >> >> >>>>>If you change hardware settings, you should >>>>> >>>>> >>also maintain the same >> >> >>>>>settings on both ends of the wire, i.e. at >>>>> >>>>> >>the computer *and* the >> >> >>>>>ethernet switch. >>>>> >>>>> >>>>> >>>>> >>>>[SNIP] >>>> >>>>I just forced it to use 100baseTX / >>>>full-duplex which I think was used before I >>>> >>>> >>forced it as well. >> >> >>>> >>>> >>>> >>>> >>>That's exactly what I ment. If you force your >>> >>> >>sk0 to 100-full do the same with >> >> >>>your switch. If you set sk0 to auto-config -- >>> >>> >>do it with your switch. >> >> >>>Watch your interface-counters: >>> >>>netstat -I sk0 -b -d -t >>> >>>If the hardware (cards, cabeling, plugs, ...) >>> >>> >>is ok, there shouldn't be any >> >> >>>errors for days or even weeks! >>> >>>Regards, >>>bh >>> >>> >>> >>> >>Hi Bernhard, >> >>thanks for your message. I suppose we all know >>something about >>networking, but this is hardware/driver related >>problem ( with the >>highest probability ). I used my server in two >>different environments - >>at home and now at serverhouse. No difference. >>Still getting (from time to time ): >> >>sk0: watchdog timeout >>sk0: link state changed to DOWN >>sk0: watchdog timeout >>sk0: link state changed to UP >>sk0: watchdog timeout >>sk0: link state changed to DOWN >>sk0: watchdog timeout >>sk0: link state changed to UP >>sk0: watchdog timeout >>sk0: link state changed to DOWN >> >>messages. But server still running. I am out of >>ideas how can we solve >>our problem and I am about to buy new network >>card, because this >>stressfull situation is not good. ;-) >> >>Vladimir >> >> > >There are generally 2 cases in which you'll get a >watchdog timeout message on a network card >driver. > >1) Your machine is in livelock (ie overrun) >2) There is a problem with the interrupts > >Clearly you should know if 1) was occurring. With >2), it could be a driver or hardware problem or >both. > >DT > > > Hi, thanks for reply. The first case ( overrun ) is impossible, the server has (for now) very low traffic ( load is 0.00 almost all the time ). The second case is right answer. ;-) I suspect driver related problem. Before FreeBSD 6.0, there were Linux Debian and I didn`t mentioned any problem. I had there for several days FreeBSD 5.4 and watchdogs appear too. Vladimir