All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: tx flush bugs, at least in my firmware.
Date: Mon, 12 May 2014 09:25:23 -0700	[thread overview]
Message-ID: <5370F5F3.3030508@candelatech.com> (raw)

Just FYI, I have no idea if this problem is with my patches, my
firwmare, or what.  At any rate, it is unlikely to be reproducible on
upstream firmware due to its limitations in numbers of VIFS supported.

Here is the problem:

Previous to today, I was using wpa_supplicant that had sharing of scan results
mostly disabled.  It would only associate a single station VIF at a time, and
mostly things were working up to 36 stations (yeah, I managed to eke out another
4 stations :)).

But today, I started fixing the scan result sharing to work like it used to work
back when I mostly tested ath9k systems.

Now, after 20-25 or so stations vifs are associated (and most of the first 20 would
be associating concurrently as possible), I get the errors below and ath10k is
effectively hung:

ath10k: failed to flush transmit queue (skip 0 ar-state 1): 0

This is very repeatable.

My kernel does not have the latest two series of patches that Michal
posted that deal with reset issues, so maybe they hold the key.

So, I'm going to dig into this, but thought I'd throw this out in case
anyone else is seeing something similar.

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

                 reply	other threads:[~2014-05-12 16:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5370F5F3.3030508@candelatech.com \
    --to=greearb@candelatech.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.