From owner-freebsd-current@FreeBSD.ORG Wed Aug 23 09:37:44 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D86416A4DD for ; Wed, 23 Aug 2006 09:37:44 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B24D43D45 for ; Wed, 23 Aug 2006 09:37:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7N9bf9Z074455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Aug 2006 13:37:41 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7N9bfi9074454; Wed, 23 Aug 2006 13:37:41 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 23 Aug 2006 13:37:41 +0400 From: Gleb Smirnoff To: Pyun YongHyeon Message-ID: <20060823093741.GF96644@FreeBSD.org> References: <20060822042023.GC12848@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060822042023.GC12848@cdnetworks.co.kr> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org Subject: Re: call for bge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2006 09:37:44 -0000 On Tue, Aug 22, 2006 at 01:20:23PM +0900, Pyun YongHyeon wrote: P> After fixing em(4) watchdog bug, I looked over bge(4) and I think P> bge(4) may suffer from the same issue. So if you have seen occasional P> watchdog timeout errors on bge(4) please give the attached patch a try. P> The patch does fix false watchdog timeout error only. P> Typical pheonoma for false watchdog timeout error are P> o polling(4) fix the issue P> o random watchdog error P> P> If my patch fix the issue you could see the following messages. P> "missing Tx completion interrupt!" or "link lost -- resetting" I still think that this fix is incorrect. It is just a more gentle recovery from a fake watchdog timeout. The more I think, the more I doubt that we really need the watchdog infrastructure that comes from old days. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE