From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 20:01:03 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 4D3DE16A41F for ; Tue, 26 Jul 2005 20:01:03 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BEE643D45 for ; Tue, 26 Jul 2005 20:01:02 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr12.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6QK0xPC006170; Tue, 26 Jul 2005 22:01:00 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j6QK0x8F047515; Tue, 26 Jul 2005 22:00:59 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j6QK0x7s047514; Tue, 26 Jul 2005 22:00:59 +0200 (CEST) (envelope-from wb) Date: Tue, 26 Jul 2005 22:00:59 +0200 From: Wilko Bulte To: Brooks Davis Message-ID: <20050726200059.GA47478@freebie.xs4all.nl> 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> <20050726193324.GA4603@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050726193324.GA4603@odin.ac.hmc.edu> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Mike Jakubik , 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 20:01:03 -0000 On Tue, Jul 26, 2005 at 12:33:24PM -0700, Brooks Davis wrote.. > On Mon, Jul 25, 2005 at 10:39:09PM -0400, Mike Jakubik wrote: > > 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. > > Could you see what happens if you run dhclient in the foreground? Just > running "dhclient -d xl0" should do it. I'd like to know what sort of > output it's generating. In my case it is not displaying anything: chuck#dhclient -d ath0 DHCPREQUEST on ath0 to 255.255.255.255 port 67 DHCPACK from 192.168.5.254 bound to 192.168.5.20 -- renewal in 21600 seconds. I can tell the phenomenon occurs when my laptop fan springs to life: CPU states: 96.5% user, 0.0% nice, 2.7% system, 0.8% interrupt, 0.0% idle Mem: 48M Active, 28M Inact, 50M Wired, 680K Cache, 34M Buf, 115M Free Swap: 257M Total, 257M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 719 _dhcp 1 129 0 1384K 1092K RUN 2:14 93.55% dhclient 607 root 1 98 0 34584K 21212K select 0:09 1.81% Xorg 663 wb 4 20 0 46712K 40224K kserel 0:27 0.00% mozilla-bin 503 root 1 8 0 1184K 796K nanslp 0:07 0.00% powerd Took (best guess) approx 5-10 minutes for the effect to kick in. -- Wilko Bulte wilko@FreeBSD.org