ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>, ath10k <ath10k@lists.infradead.org>
Subject: Re: Trouble connecting to broadcom AC APs?
Date: Thu, 20 Mar 2014 16:27:14 -0700	[thread overview]
Message-ID: <532B7952.5020800@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmom2y=7kvjY6587+93b4Yp8BChbAcfuWfdqs1sgPHXiu0g@mail.gmail.com>

On 03/20/2014 12:26 PM, Adrian Chadd wrote:
> Is the broadcom ap doing sane or insane things with the sleep bits in
> transmitted frames?
> 
> Is this a problem with 11ac only?

ath9k stations connect just fine, so it's either something with
the ath10k (including our modified firmware), or the AP has issues
with AC specifically.

Thanks,
Ben

> 
> 
> -a
> 
> 
> On 20 March 2014 12:23, Ben Greear <greearb@candelatech.com> wrote:
>> On 03/20/2014 12:17 PM, Adrian Chadd wrote:
>>> Did the per-rate transmit statistics ever make it into the firmware / driver?
>>>
>>> I'd start by looking at what rate(s) it's trying and what the transmit
>>> completion statistics say. It could be doing something exceedingly
>>> dumb like transmitting on an invalid rate or stream setup.
>>>
>>> Same deal with STBC/LDPC. Try disabling those; see what happens.
>>
>> It appears the packets get to the AP, and AP at least tries to
>> respond.
>>
>> If we bring up stations one at a time instead of multiple at once
>> it works better, and using ddwrt works better than stock firmware
>> on the AP too.
>>
>> Anyone know how well monitor mode works on ath10k?  Would be nice
>> to see what is actually on the air.
>>
>> Truth is, my main concern now is some issue with tx flush hanging,
>> so it may be a bit until I can dig closely into the issues
>> with the BCM APs.
>>
>> Thanks,
>> Ben
>>
>>>
>>>
>>>
>>> -a
>>>
>>>
>>> On 20 March 2014 08:59, Ben Greear <greearb@candelatech.com> wrote:
>>>> On 03/19/2014 11:36 PM, Kalle Valo wrote:
>>>>> Ben Greear <greearb@candelatech.com> writes:
>>>>>
>>>>>> We are seeing various funny things when trying to connect
>>>>>> ath10k stations to commercial APs with broadcom AC NICs.
>>>>>>
>>>>>> It sort of works sometimes, but we often see failure to
>>>>>> acquire DHCP lease in a timely manner, etc.
>>>>>
>>>>> So it's a problem with broadcast frames? With or without encryption? Did
>>>>> you try disabling power save?
>>>>
>>>> With and without encryption we see issues.  I am disabling power-save,
>>>> but from poking around in firmware, I'm not sure how much affect that
>>>> has.
>>>>
>>>> I'm using commands like this to disable it:
>>>> ./local/sbin/iw dev sta219 set power_save off
>>>>
>>>>>> Similar testing on APs using QCA AC NICs appears to work
>>>>>> much better.
>>>>>>
>>>>>> Our problems could be most anything, including the fact that this
>>>>>> testing is done on our modified firmware, but I am curious if anyone
>>>>>> else seems any similar issues?
>>>>>
>>>>> Occasionally I test connecting to D-Link DIR-865L in STA mode. But I
>>>>> just do just simple ping tests and with manual IPs.
>>>>
>>>> We'll keep poking at things and see if we can find any
>>>> pattern or work around.
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>> --
>>>> Ben Greear <greearb@candelatech.com>
>>>> Candela Technologies Inc  http://www.candelatech.com
>>>>
>>>>
>>>> _______________________________________________
>>>> ath10k mailing list
>>>> ath10k@lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>
>>
>> --
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>>
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-03-20 23:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 17:01 Trouble connecting to broadcom AC APs? Ben Greear
2014-03-20  6:36 ` Kalle Valo
2014-03-20 15:59   ` Ben Greear
2014-03-20 19:17     ` Adrian Chadd
2014-03-20 19:23       ` Ben Greear
2014-03-20 19:26         ` Adrian Chadd
2014-03-20 23:27           ` Ben Greear [this message]
2014-03-20 23:34             ` Adrian Chadd
2014-03-21  6:01         ` Janusz Dziedzic
2014-03-21  7:07           ` Janusz Dziedzic
2014-03-21 17:41             ` Ben Greear
2014-03-24 19:45               ` Janusz Dziedzic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=532B7952.5020800@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox