dhclient taking all cpu
Mike Jakubik
mikej at rogers.com
Tue Jul 26 02:39:10 GMT 2005
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.
More information about the freebsd-current
mailing list