From owner-freebsd-questions@FreeBSD.ORG Wed Aug 2 00:00:44 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 CC1CC16A4DF for ; Wed, 2 Aug 2006 00:00:44 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A85143D49 for ; Wed, 2 Aug 2006 00:00:44 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from localhost (monrovll-cuda1-24-53-251-44.pittpa.adelphia.net [24.53.251.44]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 01 Aug 2006 20:00:43 -0400 id 00056419.44CFEB2B.0001453C Date: Tue, 1 Aug 2006 20:00:42 -0400 From: Bill Moran To: freebsd-questions@freebsd.org Message-Id: <20060801200042.8af51559.wmoran@collaborativefusion.com> In-Reply-To: <200608020052.23836.list-freebsd-2004@morbius.sent.com> References: <20060801193945.83338.qmail@web25219.mail.ukl.yahoo.com> <200608020052.23836.list-freebsd-2004@morbius.sent.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.19; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 00:00:44 -0000 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. But I'm no expert ... I could be wrong. -- Bill Moran MAL: Hell, this job I would pull for free. ZOE: Can I have your share? MAL: No. ZOE: If you die, can I have your share? MAL: Yes.