From owner-freebsd-questions@FreeBSD.ORG Sat Jan 10 14:51:46 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B29F10656C4 for ; Sat, 10 Jan 2009 14:51:46 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id 724EF8FC14 for ; Sat, 10 Jan 2009 14:51:46 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 23704 invoked from network); 10 Jan 2009 14:51:44 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Jan 2009 14:51:43 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id AC38450842; Sat, 10 Jan 2009 09:51:40 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 48DEF1CDEB; Sat, 10 Jan 2009 09:51:40 -0500 (EST) To: Frank Bonnet References: <49670974.2060202@esiee.fr> From: Lowell Gilbert Date: Sat, 10 Jan 2009 09:51:40 -0500 In-Reply-To: <49670974.2060202@esiee.fr> (Frank Bonnet's message of "Fri\, 09 Jan 2009 09\:23\:16 +0100") Message-ID: <44sknr2ozn.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: 7.1 : watchdog bge0 timeout ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 14:51:47 -0000 Frank Bonnet writes: > I've installed 7.1 onto our mail exchager (MX) then it suddendly stopped > to work last night with the following message > > watchdog bge0 timeout > > > The machine is a HP pc which was doing the same service at 6.3 without > that kind of trouble Could be hardware trouble, I suppose. The whole point of a watchdog is to let the driver recover after the hardware has locked up. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/