From: Ben Gamari <bgamari@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: race conditions in dma
Date: Mon, 01 Nov 2010 11:43:41 -0400 [thread overview]
Message-ID: <8762whrqvm.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTik=LvRZja13SGOpicVjbyf6chRtTD-RkvSm2VcE@mail.gmail.com>
On Mon, 1 Nov 2010 16:17:23 +0100, Bj?rn Smedman <bjorn.smedman@venatech.se> wrote:
> Hi all,
>
> I have an application that creates and destroys a lot of ap vifs and
> does a lot of monitor frame injection. The recent ath9k rx locking
> fixes have helped with stability in this use-case but there still
> seems to be some tx/beacon related race condition(s). These manifests
> themselves as follows on an AR913x based router running
> compat-wireless-2010-10-19 (with locking fixes etc from openwrt):
>
> 1. TX DMA hangs under simultaneous high RX and TX load
> 2. TX is completely hung but chip is never reset
I have also observed both of these behaviors with just a standard
hostapd single VIF configuration. Quite annoying. It seems to be better
with recent wireless-testing trees.
- Ben
WARNING: multiple messages have this Message-ID (diff)
From: Ben Gamari <bgamari@gmail.com>
To: "Björn Smedman" <bjorn.smedman@venatech.se>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] ath9k: race conditions in dma
Date: Mon, 01 Nov 2010 11:43:41 -0400 [thread overview]
Message-ID: <8762whrqvm.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTik=LvRZja13SGOpicVjbyf6chRtTD-RkvSm2VcE@mail.gmail.com>
On Mon, 1 Nov 2010 16:17:23 +0100, Björn Smedman <bjorn.smedman@venatech.se> wrote:
> Hi all,
>
> I have an application that creates and destroys a lot of ap vifs and
> does a lot of monitor frame injection. The recent ath9k rx locking
> fixes have helped with stability in this use-case but there still
> seems to be some tx/beacon related race condition(s). These manifests
> themselves as follows on an AR913x based router running
> compat-wireless-2010-10-19 (with locking fixes etc from openwrt):
>
> 1. TX DMA hangs under simultaneous high RX and TX load
> 2. TX is completely hung but chip is never reset
I have also observed both of these behaviors with just a standard
hostapd single VIF configuration. Quite annoying. It seems to be better
with recent wireless-testing trees.
- Ben
next prev parent reply other threads:[~2010-11-01 15:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 15:17 [ath9k-devel] ath9k: race conditions in dma Björn Smedman
2010-11-01 15:17 ` Björn Smedman
2010-11-01 15:43 ` Ben Gamari [this message]
2010-11-01 15:43 ` [ath9k-devel] " Ben Gamari
2010-11-01 15:50 ` Björn Smedman
2010-11-01 15:50 ` Björn Smedman
2010-11-01 23:12 ` Peter Stuge
2010-11-01 23:12 ` Peter Stuge
2010-11-01 16:20 ` Björn Smedman
2010-11-01 16:20 ` Björn Smedman
2010-11-01 16:39 ` Björn Smedman
2010-11-01 16:39 ` Björn Smedman
2010-11-01 16:44 ` Luis R. Rodriguez
2010-11-01 16:44 ` Luis R. Rodriguez
2010-11-01 16:52 ` Felix Fietkau
2010-11-01 16:52 ` Felix Fietkau
2010-11-01 17:12 ` Björn Smedman
2010-11-01 17:12 ` Björn Smedman
2010-11-02 16:55 ` Björn Smedman
2010-11-02 16:55 ` Björn Smedman
2010-11-03 16:41 ` Björn Smedman
2010-11-03 16:41 ` Björn Smedman
2010-11-03 17:47 ` Ben Gamari
2010-11-03 17:47 ` Ben Gamari
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=8762whrqvm.fsf@gmail.com \
--to=bgamari@gmail.com \
--cc=ath9k-devel@lists.ath9k.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.