From owner-freebsd-questions@FreeBSD.ORG Wed Aug 2 12:29:28 2006 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 96C2C16A4DD for ; Wed, 2 Aug 2006 12:29:28 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26D1543D53 for ; Wed, 2 Aug 2006 12:29:27 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.145] (helo=anti-virus03-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1G8Fqo-0006u4-5X; Wed, 02 Aug 2006 13:29:26 +0100 Received: from [82.41.35.166] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1G8Fqn-00055R-LK; Wed, 02 Aug 2006 13:29:25 +0100 Message-ID: <44D09AA5.1000507@dial.pipex.com> Date: Wed, 02 Aug 2006 13:29:25 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20060801193945.83338.qmail@web25219.mail.ukl.yahoo.com> <200608020052.23836.list-freebsd-2004@morbius.sent.com> <20060801200042.8af51559.wmoran@collaborativefusion.com> In-Reply-To: <20060801200042.8af51559.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: watchdog question. 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: Wed, 02 Aug 2006 12:29:28 -0000 Bill Moran wrote: >RW wrote: > > > >>On Tuesday 01 August 2006 20:39, Efren Bravo wrote: >> >> >>>Hi, >>> >>>I've a freeBSD box and I've been seeing this >>>message for several months: sis0 watchdog >>>timeout. >>> >>>The box has two ethernet cards, sis0 (100mb) and >>>vr0 (10mb). >>> >>>The messages isn't frequent but yesterday it got >>>my attention. What does this mean? >>> >>> >>from sis(4) >> sis%d: watchdog timeout The device has stopped responding to the net- >> work, or there is a problem with the network connection (e.g. a cable >> fault). >> >> > >I've seen this frequently with sis cards. My opinion is that all sis >cards are cheapo crap, and watchdog timer is a workaround to try to make >them work in spite of being crap. I've seen sis cards in Windows machines >and they perform lousy there as well. > > I always got these errors on sis cards too - always ignored then. Worked fine for me on a lightly loaded network. If you start getting real symptoms - card locking up for example - then you;ll have to get a better network card. But unless and until that happens I would ignore it. --Alex