On Mon, Jul 25, 2005 at 09:45:39PM -0400, Mike Jakubik wrote: > Brooks Davis wrote: > > >On Mon, Jul 25, 2005 at 08:12:55PM -0400, Mike Jakubik wrote: > > > > > >>Why is dhclient taking over 80% of CPU, constantly? > >> > >> PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > >> 216 _dhcp 1 132 0 1448K 956K RUN 17.5H 83.30% > >>dhclient > >> > >>FreeBSD 7.0-CURRENT #0: Mon Jul 25 00:23:30 EDT 2005 > >> > >> > > > >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. -- Brooks -- 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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:39 UTC