All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Receiving your own wifi beacons
Date: Mon, 12 May 2014 08:47:50 +0300	[thread overview]
Message-ID: <87fvkfim49.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-3dREsfjYR_2rpDxjeKEy8ZwqEZ9yXXYtoB8J92AqGB9A@mail.gmail.com> (Avery Pennarun's message of "Mon, 12 May 2014 01:29:57 -0400")

Avery Pennarun <apenwarr@gmail.com> writes:

> On Mon, May 12, 2014 at 12:50 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Avery Pennarun <apenwarr@gmail.com> writes:
>>> We're currently investigating a problem where the ath10k AP will
>>> seemingly stop sending out beacons, with no other obvious symptoms
>>> (hostapd is still working fine).  There's not much I can report
>>> because, of course, no symptoms.
>>
>> Can you still provide more information about the problem, please? How
>> often do you see it? What kind of setup do you have? With or without
>> DFS? How many BSS?
>
> It doesn't happen often.  We haven't been able to reproduce it in a
> lab, only at a small number of our test sites at people's homes, and
> even then only rarely (although some people apparently experience it
> more than others).

Ok, so this will a tricky problem to solve.

> We aren't using DFS (does ath10k even support DFS yet?). 

Yes, ath10k supports DFS on ETSI channels but only with one BSS. Michal
has been working on mac80211 DFS with multiple BSS support and he is
getting close to finish that. And I'm hoping to get FCC and MKK support
to ath.ko soon.

> We are using 20 MHz channel, 5 GHz for all these test users. There is
> only a single BSS configured for our APs right now, although other APs
> may be nearby.

The only thing out of ordinary is the 20 MHz channel, as I think most of
users use VHT80 configuration. But I'm having hard time to believe that
would be reason why only you see it. (This is the first time I hear
about a problem like this with ath10k.)

> Based on Michal's suggestion, we've added some code to enable minimal
> debug messages from the firmware and log whenever a beacon is sent.
> This seems to work, so we'll deploy it to all our test users in the
> next week or so and, if the problem triggers, at least this should
> give us a clue (such as whether the firmware thinks it's still sending
> beacons, and exactly what the dmesg looks like at the time that it
> stops).

Good.

> If you have any other suggestions, please let us know.

Do you know if interrupts are still working when the problem appears?
What about other ath10k functionality and driver's communication to the
firmware, is that working normally? For example, can you retrieve stats
from firmware when the issue happens?

-- 
Kalle Valo

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

  reply	other threads:[~2014-05-12  5:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 23:42 Receiving your own wifi beacons Avery Pennarun
2014-05-07  1:18 ` Yeoh Chun-Yeow
2014-05-07  1:32   ` Avery Pennarun
2014-05-07  6:23 ` Michal Kazior
2014-05-12  4:50 ` Kalle Valo
2014-05-12  5:29   ` Avery Pennarun
2014-05-12  5:47     ` Kalle Valo [this message]
2014-05-12  6:21       ` Avery Pennarun

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=87fvkfim49.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=apenwarr@gmail.com \
    --cc=ath10k@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.