All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Kazior <michal.kazior@tieto.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Probe Response packets sometimes delayed by 200ms
Date: Fri, 3 Oct 2014 08:10:46 +0200	[thread overview]
Message-ID: <CA+BoTQmeMNz2PvT9Si_smYqL24OBA+JX8fJORnp5hck0x7eP2g@mail.gmail.com> (raw)
In-Reply-To: <CAHqTa-2yz13WAgvXxJVYMXQ7fVqRtuQ8ABAC6vKv07=fne_YGw@mail.gmail.com>

On 3 October 2014 07:48, Avery Pennarun <apenwarr@gmail.com> wrote:
> Hi all,
>
> We're chasing a problem where, with an ath10k device running as access
> point and a Macbook Air as a client, responses to probe requests are
> sometimes missed by the Macbook Air because they are delayed for a
> long time, and the Macbook has changed channels by the time they come
> through.
>
> ath10k driver version: from backports as of kvalo/ath-next on
> 2014-03-08 (v3.15-rc1-237-gd9bc4b9)
>
> Firmware version: 10.1.467.3
>
> Steps:
> - start capturing packets, either on the ath10k AP itself or a
> secondary monitor system
> - on the Macbook Air (which has joined your SSID at least once
> before), open and close the wifi dropdown menu a few times.  (May also
> happen with clients other than Macbook Air; not heavily tested.)

Was the Macbook Air disconnected cleanly on the AP?

There's a tx credit starvation bug which blocks wmi commands after
disassoc+deauth frames are queued (via wmi as well) and aren't acked
by station in which case wmi peer delete command times out and
sta_state splats a calltrace in kernel logs. This effectively leaves
firmware thinking the peer is still connected and it is never
disconnected (you can expect spurious sta kickout events after an hour
once that happens). This could explain why ath10k AP tries to play
powersave with the Macbook Air.

Or perhaps this is related to uAPSD? Do you have it enabled in
hostapd? Is Macbook Air associating with uAPSD enabled?

Or maybe firmwar expects host driver should reset some ap-sta
powersave related settings before deleting peer entries.

I don't have any other ideas now.


Michał

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

  reply	other threads:[~2014-10-03  6:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03  5:48 Probe Response packets sometimes delayed by 200ms Avery Pennarun
2014-10-03  6:10 ` Michal Kazior [this message]
2014-10-03  6:39   ` Avery Pennarun
2014-10-03  7:37     ` Michal Kazior
2014-10-04  3:02       ` 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=CA+BoTQmeMNz2PvT9Si_smYqL24OBA+JX8fJORnp5hck0x7eP2g@mail.gmail.com \
    --to=michal.kazior@tieto.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.