Denton Gentry writes:
> I built an image with the 10.2 firmware and left it running with two
> clients disassociating and reassociating every few seconds. After 8
> hours I stopped it, with no failures detected.
>
> I restored the 10.1 firmware, and it failed in 9 minutes. There is a
> substantia
On Sun, Aug 24, 2014 at 11:59 PM, Kalle Valo wrote:
> Denton Gentry writes:
>
>> [ 18.047597] ath10k: qca988x hw2.0 (0x4100016c, 0x043202ff) fw
>> 10.1.467.2-1 api 2 htt 2.1
>>
>> On Sun, Aug 24, 2014 at 7:22 PM, Adrian Chadd wrote:
>>> Which firmware build are you using?
>
> (Standard whining
Denton Gentry writes:
> [ 18.047597] ath10k: qca988x hw2.0 (0x4100016c, 0x043202ff) fw
> 10.1.467.2-1 api 2 htt 2.1
>
> On Sun, Aug 24, 2014 at 7:22 PM, Adrian Chadd wrote:
>> Which firmware build are you using?
(Standard whining: top posting is annoying.)
Denton, any chance you could test w
[ 18.047597] ath10k: qca988x hw2.0 (0x4100016c, 0x043202ff) fw
10.1.467.2-1 api 2 htt 2.1
On Sun, Aug 24, 2014 at 7:22 PM, Adrian Chadd wrote:
> Which firmware build are you using?
>
>
>
> -a
>
>
> On 24 August 2014 19:17, Denton Gentry wrote:
>> I have an AP using ath10k as a 5 GHz 802.11ac i
Which firmware build are you using?
-a
On 24 August 2014 19:17, Denton Gentry wrote:
> I have an AP using ath10k as a 5 GHz 802.11ac interface. Very
> occasionally it gets into a mode where stations are unable to
> associate. I don’t know how it gets into this mode, but once there the
> seque
I have an AP using ath10k as a 5 GHz 802.11ac interface. Very
occasionally it gets into a mode where stations are unable to
associate. I don’t know how it gets into this mode, but once there the
sequence of events when a client tries to associate is:
1. Client and AP exchange Authentication, Assoc
