ath/wpa_supplicant/dhclient lost connection

Samuel J. Greear sjg at evilcode.net
Mon Oct 25 23:32:12 PDT 2010


On Tue, Oct 26, 2010 at 12:17 AM, Matthias Schmidt
<matthias at dragonflybsd.org> wrote:
> * elekktretterr at exemail.com.au wrote:
>> Hi,
>>
>> This is on i386/master from about a week ago. It's an SMP laptop. For some
>> reason after about 6 hours of running, wireless drops out, but
>> wpa_supplicant is still running, and dhclient is running at near 100% CPU.
>> It's fixed by kill -HUP wpa_supplicant and dhclient to bring the network
>> up and reacquire IP.
>>
>> Anyone experiencing similar a issue?
>
> Yes, I saw the same behavior on an IBM Thinkpad T42 UP running i386
> master.  Killing the dhclient helps.
>
> Cheers
>
>        Matthias
>

Recent master kernel -and- world?

If this is seen again, truss or ktrace output of dhclient would be helpful.

If you could install a debug dhclient now, in the event it happens
again you could induce a core (or at least gdb the process and get a
trace), that might prove helpful as well.

Why, specifically, does the network stop working, if you can identify
it? Default route? resolv.conf overwritten?

Thanks,
Sam






More information about the Bugs mailing list