From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFT 0/4] ath10k: fix flushing and tx stalls
Date: Sun, 06 Apr 2014 18:05:20 -0700 [thread overview]
Message-ID: <5341F9D0.2090808@candelatech.com> (raw)
In-Reply-To: <5341F1A9.2030202@candelatech.com>
On 04/06/2014 05:30 PM, Ben Greear wrote:
> On 04/04/2014 04:37 AM, Michal Kazior wrote:
>> Hi,
>>
>> After digging around I've found what seems to be
>> the problem with WMI Tx credit starvation and
>> inability to properly flush Tx in ath10k_flush().
>
> I applied all four, rebooted AP and Station machine with the
> new kernel (3.14.0-wl-ath+). I had removed my own tx-hang detection
> hack.
Looks like the problems start with patch 3/4.
All tests were done with all 4 patches applied on the AP machine,
and it appears that works fine. The station machine worked fine with
the first two patches, but when third was applied, only a few stations
come up and I get behaviour similar to that described in the first email,
but I do not see anything obviously wrong in dmesg...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-04-07 1:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 11:37 [RFT 0/4] ath10k: fix flushing and tx stalls Michal Kazior
2014-04-04 11:37 ` [RFT 1/4] ath10k: fix wmi-htc tx credit starvation Michal Kazior
2014-04-04 11:37 ` [RFT 2/4] ath10k: rework peer accounting Michal Kazior
2014-04-04 11:37 ` [RFT 3/4] ath10k: wait for mgmt tx when flushing too Michal Kazior
2014-04-04 11:37 ` [RFT 4/4] ath10k: improve tx flushing Michal Kazior
2014-04-08 6:58 ` Kalle Valo
2014-04-04 14:49 ` [RFT 0/4] ath10k: fix flushing and tx stalls Ben Greear
2014-04-04 18:31 ` Dave Taht
2014-04-07 9:06 ` Michal Kazior
2014-04-07 0:30 ` Ben Greear
2014-04-07 1:05 ` Ben Greear [this message]
2014-04-07 9:11 ` Michal Kazior
2014-04-08 2:31 ` Ben Greear
2014-04-08 5:51 ` Michal Kazior
2014-04-08 16:02 ` Ben Greear
2014-04-09 6:25 ` Michal Kazior
2014-04-09 17:34 ` Ben Greear
2014-04-09 19:29 ` Ben Greear
2014-04-10 3:45 ` Kalle Valo
2014-04-09 10:48 ` [RFTv2 0/5] ath10k: " Michal Kazior
2014-04-09 10:48 ` [RFTv2 1/5] ath10k: always request htc tx replenishment Michal Kazior
2014-04-09 10:48 ` [RFTv2 2/5] ath10k: fix wmi-htc tx credit starvation Michal Kazior
2015-01-29 1:32 ` YanBo
2015-01-29 7:57 ` Michal Kazior
2015-01-29 16:50 ` Ben Greear
2014-04-09 10:48 ` [RFTv2 3/5] ath10k: rework peer accounting Michal Kazior
2014-04-10 6:50 ` Kalle Valo
2014-04-10 6:56 ` Michal Kazior
2014-04-10 6:59 ` Kalle Valo
2014-04-10 7:11 ` Michal Kazior
2014-04-10 7:18 ` Kalle Valo
2014-04-10 7:43 ` Michal Kazior
2014-04-11 6:22 ` Kalle Valo
2014-04-11 6:31 ` Kalle Valo
2014-04-11 4:59 ` Ben Greear
2014-04-09 10:48 ` [RFTv2 4/5] ath10k: wait for mgmt tx when flushing too Michal Kazior
2014-04-09 10:48 ` [RFTv2 5/5] ath10k: improve tx flushing Michal Kazior
2014-04-09 21:46 ` [RFTv2 0/5] ath10k: ath10k: fix flushing and tx stalls Ben Greear
2014-04-09 23:58 ` Ben Greear
2014-04-10 5:10 ` Michal Kazior
2014-04-10 5:26 ` Ben Greear
2014-04-10 8:50 ` Michal Kazior
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=5341F9D0.2090808@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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;
as well as URLs for NNTP newsgroup(s).