From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 05:10:27 2005 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 C681416A41F for ; Wed, 27 Jul 2005 05:10:27 +0000 (GMT) (envelope-from caelian@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E63143D46 for ; Wed, 27 Jul 2005 05:10:27 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so91392nzo for ; Tue, 26 Jul 2005 22:10:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Y/fJsTTcIdp9kLM1p2D4bq7jnqvZQx3jQkG7TFF1xKwTXL7MC33dx5uy+vMpbI5HfcNLd3ouDte2x2XG9tdjz/SRg/s+JOI5rXZdweNKggkd+4VNomTqEv/Dq+kBLBG9BePY1pkQb2/Bg99e/3AA0lPySHryOXUyb+6YAESCb18= Received: by 10.36.8.10 with SMTP id 10mr544226nzh; Tue, 26 Jul 2005 22:10:26 -0700 (PDT) Received: from ?192.168.15.103? ([68.190.230.198]) by mx.gmail.com with ESMTP id 37sm582942nzf.2005.07.26.22.10.25; Tue, 26 Jul 2005 22:10:26 -0700 (PDT) From: Pascal Hofstee To: Mike Jakubik In-Reply-To: <4901.172.16.0.199.1122345549.squirrel@172.16.0.1> References: <42E58007.9030202@rogers.com> <20050726004246.GA20597@odin.ac.hmc.edu> <42E595C3.2070003@rogers.com> <20050726015428.GF20597@odin.ac.hmc.edu> <4901.172.16.0.199.1122345549.squirrel@172.16.0.1> Content-Type: text/plain Date: Tue, 26 Jul 2005 22:10:19 -0700 Message-Id: <1122441019.33792.7.camel@synergy.charterpipeline.net.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.3.5.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: dhclient taking all cpu 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, 27 Jul 2005 05:10:27 -0000 On Mon, 2005-07-25 at 22:39 -0400, Mike Jakubik wrote: > It seems to be back at it again, this time it took longer to kick in. Here > is a "ps auxw|grep dhclient" : > > _dhcp 219 93.5 0.2 1484 1136 ?? Rs 8:49PM 5:06.00 dhclient: > xl0 (dhclient) > root 193 0.0 0.2 1484 1088 d0- S 8:49PM 0:00.02 dhclient: > xl0 [priv] (dhclient) Hi .. this looks exactly like the scenario i tried on my 7.0-CURRENT adm64. i manually killed any running dhclient processes, then manually started a dhclient process as root. There was no out of the ordinary output there .. but after a couple of minutes i noticed a Second dhclient process eating 64+% CPU again in top ... this second dhclient process very likely got somehow started by devd, and since my own root-started dhclient process was still running, for some reason ate 64 +% CPU. The second i killed my own manually root-started dhclient .. the devcd started dhclient dropped its CPU usage .. and hasn't been noticeable since .. for several hours at least. I still don't get Why devd insists on starting a second dhclient process a few minutes after initial launch .. but as far as i can tell that Is what's happening. Terminating the first dhclient process cancels the cpu-hogging of the second process and seems to act 'stable' from that point on. I hope somebody with a better understanding of the code at hand, may benefit from this information. -- Pascal Hofstee