From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 02:39:10 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 38F6416A41F for ; Tue, 26 Jul 2005 02:39:10 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id A553843D45 for ; Tue, 26 Jul 2005 02:39:09 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 44232 invoked from network); 26 Jul 2005 02:39:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=gjbaiupb33OSUmR6ai6e+TegerAcbkO70SHg5bmWklLYkND80PTcwr5D1jvxvSm/J1yj69G7lxxRgoIlvHGAtyUHo3IpszuLAyh9fHnFVvLREV6ryzuj9qAiXmh0qAjACA1kxezbJ1naWMDWrs5wSQTzFLt/6+E1HaAEd5EOp7c= ; Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 26 Jul 2005 02:39:08 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by 172.16.0.1 with HTTP; Mon, 25 Jul 2005 22:39:09 -0400 (EDT) Message-ID: <4901.172.16.0.199.1122345549.squirrel@172.16.0.1> In-Reply-To: <20050726015428.GF20597@odin.ac.hmc.edu> References: <42E58007.9030202@rogers.com> <20050726004246.GA20597@odin.ac.hmc.edu> <42E595C3.2070003@rogers.com> <20050726015428.GF20597@odin.ac.hmc.edu> Date: Mon, 25 Jul 2005 22:39:09 -0400 (EDT) From: "Mike Jakubik" To: "Brooks Davis" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: Tue, 26 Jul 2005 02:39:10 -0000 On Mon, July 25, 2005 9:54 pm, Brooks Davis said: >>> Probably something wrong with your interface, but you havent't >>> provided any useful information so who knows. At the very least, I >>> need to know what interface you are running on, something about it's >>> status, and if both dhclient processes are running. >>> >> The interface is xl0 (3Com 3c905C-TX Fast Etherlink XL), and it worked >> in this machine fine for as long as i remember. This seems to have >> happened since a recent cvsup and buildworld from ~6-BETA to 7-CURRENT. >> I rebooted three times, and the problem occured rougly a minute after >> bootup. On the fourth time however, it seems to be ok so far. > > That sounds like a problem with the code that handles the link state > notifications in the interface driver. The notifications are a reletivly > new feature that we're only now starting to use heavily so there are going > to be bumps in the road. It would be intresting to know if you see link > state messages promptly if you plug and unplug the network cable. 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) top: PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 219 _dhcp 1 129 0 1484K 1136K RUN 9:33 94.24% dhclient Nothing in dmesg about link state changes on xl0. Unplugging and replugging the network cable results in link state notification within a couple seconds.