From owner-freebsd-current@FreeBSD.ORG Tue Jul 25 12:43:01 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 2375116A4DD; Tue, 25 Jul 2006 12:43:01 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF24943D46; Tue, 25 Jul 2006 12:43:00 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp2-g19.free.fr (Postfix) with ESMTP id 138817597A; Tue, 25 Jul 2006 14:43:00 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 843439B983; Tue, 25 Jul 2006 12:43:28 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 7013D405F; Tue, 25 Jul 2006 14:43:28 +0200 (CEST) Date: Tue, 25 Jul 2006 14:43:28 +0200 From: Jeremie Le Hen To: Doug Barton Message-ID: <20060725124328.GI6253@obiwan.tataz.chchile.org> References: <20060721123448.GV6253@obiwan.tataz.chchile.org> <44C1CE73.7030200@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C1CE73.7030200@FreeBSD.org> User-Agent: Mutt/1.5.11 Cc: freebsd-current@FreeBSD.org Subject: Re: [fbsd] Re: em(4) watchdog timeout 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: Tue, 25 Jul 2006 12:43:01 -0000 On Sat, Jul 22, 2006 at 12:06:27AM -0700, Doug Barton wrote: > Jeremie Le Hen wrote: > > Hi, > > > > I am running a two month old current (dated from May 24) > > SOP with -current is that before you submit a bug report for a system this > old you should upgrade to the latest world and kernel. Two months is > _really_ old in -current terms. I am rebuilding a fresher one right now. According to Ian's post, the problem is likely to remain. What do you advice me to do to track this down ? FYI, my -CURRENT kernel (as well userland) is patched with ProPolice. I don't think this can lead to this kind of problem, the overhead is really small, in an order of 3 percent. Do you think such an overhead in a time-critial path could trigger a watchdog timeout ? Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >