From owner-freebsd-questions@FreeBSD.ORG Mon Aug 1 13:47:54 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 5A42816A41F for ; Mon, 1 Aug 2005 13:47:54 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6EA843D46 for ; Mon, 1 Aug 2005 13:47:53 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 28291 invoked from network); 1 Aug 2005 13:47:53 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Aug 2005 13:47:53 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id C526036; Mon, 1 Aug 2005 09:47:52 -0400 (EDT) Sender: lowell@be-well.ilk.org To: "DeadMan Xia ...." To: freebsd-questions@freebsd.org References: From: Lowell Gilbert Date: 01 Aug 2005 09:47:52 -0400 In-Reply-To: Message-ID: <44y87l22gn.fsf@be-well.ilk.org> Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: bge0 : WatchDog timeout -- resetting 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: Mon, 01 Aug 2005 13:47:54 -0000 "DeadMan Xia ...." writes: > I m using FreeBSD 5.3, on Dell Power Edge 6650 Quad Processor Machine, > my system get stuck while i m accessing it through ssh. well after > some time , when i acces the machine & check , /var/log/messages ,, i > can bge0: WatchDog Timedout -- resetting error. Is there any one , to > tap my back & get me off from this headhac,,, There is explicit support for a lot of new chips since 5.3 was released. You don't mention what you have, so we can't know for sure, but you should definitely update your system before looking more deeply into the firmware hang. And if there is a firmware update for your NIC, definitely apply that.