From owner-freebsd-questions@FreeBSD.ORG Mon Nov 28 15:52:43 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 52E3B16A41F for ; Mon, 28 Nov 2005 15:52:43 +0000 (GMT) (envelope-from danial_thom@yahoo.com) Received: from web33312.mail.mud.yahoo.com (web33312.mail.mud.yahoo.com [68.142.206.127]) by mx1.FreeBSD.org (Postfix) with SMTP id D519243D45 for ; Mon, 28 Nov 2005 15:52:42 +0000 (GMT) (envelope-from danial_thom@yahoo.com) Received: (qmail 6088 invoked by uid 60001); 28 Nov 2005 15:52:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=5l52KkJp2JclwQcPRgRTlLi4bAy68IrCrCry+XQ0+T66l2eI2ITyNd7z5bOjfWzXkBYoW+/IYe2zan1SFtawTG9ZPvYtfmCZOm3lCyegv/9hKwuVRMGUgg7gXPqpxbf0EhObYGymIlw8/tJ/ErezIZZ11hnj0P76XEbneuWa9gc= ; Message-ID: <20051128155242.6086.qmail@web33312.mail.mud.yahoo.com> Received: from [24.46.186.215] by web33312.mail.mud.yahoo.com via HTTP; Mon, 28 Nov 2005 07:52:41 PST Date: Mon, 28 Nov 2005 07:52:41 -0800 (PST) From: Danial Thom To: Vladimir Dvorak , Bernhard Fischer In-Reply-To: <438AF4AC.40304@vdsoft.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: 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 Reply-To: danial_thom@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 15:52:43 -0000 --- 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 __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs