Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Aug 2012 08:38:56 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: New ath code works well as AP
Message-ID:  <CAJ-VmokyTZyEEeodfmzFzA07tGVAu6QJHxNBWbrJpEMUb_Etig@mail.gmail.com>
In-Reply-To: <20120820125524.GL98910@zxy.spb.ru>
References:  <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <CAJ-Vmompt74rHx=C8Z5L978ciFN1LnPr2Mz=5PB3a%2BdgZJ8GVA@mail.gmail.com> <20120820125524.GL98910@zxy.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On 20 August 2012 05:55, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:

> wlan0: link state changed to DOWN/UP -- because AP don't implement
> 802.11R and don't transmit WLAN_EID_TIMEOUT_INTERVAL.

So you mean that's to be expected? There are situations where an AP
will time a station out. May leave a background ping going and see if
it stays associated?

>> > [155821] ath0: bb hang detected (0x4), resetting
>> > [194052] ath0: device timeout
>> > [202568] ath0: device timeout
>> > [214975] ath0: bb hang detected (0x4), resetting
>
> And time to time I need to
>
> kldunload if_ath_pci.ko
> kldload if_ath_pci.ko
>
> for re-enable card.

This is a bit more worrying. An ifconfig wlanX destroy ; ifconfig
wlanX create isn't sufficient?



Adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokyTZyEEeodfmzFzA07tGVAu6QJHxNBWbrJpEMUb_Etig>