Date: Tue, 26 Jul 2005 12:33:24 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Mike Jakubik <mikej@rogers.com> Cc: freebsd-current@freebsd.org Subject: Re: dhclient taking all cpu Message-ID: <20050726193324.GA4603@odin.ac.hmc.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 25, 2005 at 10:39:09PM -0400, Mike Jakubik wrote: > On Mon, July 25, 2005 9:54 pm, Brooks Davis said: >=20 > >>> 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 reletiv= ly > > new feature that we're only now starting to use heavily so there are go= ing > > 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. >=20 > It seems to be back at it again, this time it took longer to kick in. Here > is a "ps auxw|grep dhclient" : >=20 > _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) >=20 > top: >=20 > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMA= ND > 219 _dhcp 1 129 0 1484K 1136K RUN 9:33 94.24% dhcli= ent >=20 > 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. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC5o/+XY6L6fI4GtQRAnxvAKC/Fn6/rp7Ggz9jLwBD9dDoZlNPjgCeKMVU 3MbAQWJ9S43Tbwqb1UiNlbc= =/x4h -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050726193324.GA4603>