From: Peter Stuge <peter@stuge.se>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: Ben Gamari <bgamari@gmail.com>,
ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] ath9k: race conditions in dma
Date: Tue, 2 Nov 2010 00:12:20 +0100 [thread overview]
Message-ID: <20101101231220.8591.qmail@stuge.se> (raw)
In-Reply-To: <AANLkTins=0vM=+qpdDB2-KvMBq6J5vwUjn6Ni76GyQst@mail.gmail.com>
Björn Smedman wrote:
> >> 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.
>
> Thanx Ben, it's a relief to know I'm not the only one suffering
> from this.
Just a note to confirm that I have also seen many different failures
related to this. The lasting impression is that it's a big mess.
I bought my first ath9k hardware roughly a year ago. That was totally
useless as STA up until kernels a few months ago. I am now using an
AR9280 card and for the very first time ath9k hardware and driver is
actually working at all for me, but there are still issues as I noted
in the other email.
Unfortunately they're the kind of issues which can't be debugged much
lacking strong knowledge of device internals.
//Peter
next prev parent reply other threads:[~2010-11-01 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 15:17 ath9k: race conditions in dma Björn Smedman
2010-11-01 15:43 ` [ath9k-devel] " Ben Gamari
2010-11-01 15:50 ` Björn Smedman
2010-11-01 23:12 ` Peter Stuge [this message]
2010-11-01 16:20 ` Björn Smedman
2010-11-01 16:39 ` Björn Smedman
2010-11-01 16:44 ` Luis R. Rodriguez
2010-11-01 16:52 ` Felix Fietkau
2010-11-01 17:12 ` Björn Smedman
2010-11-02 16:55 ` Björn Smedman
2010-11-03 16:41 ` Björn Smedman
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=20101101231220.8591.qmail@stuge.se \
--to=peter@stuge.se \
--cc=ath9k-devel@lists.ath9k.org \
--cc=bgamari@gmail.com \
--cc=bjorn.smedman@venatech.se \
--cc=linux-wireless@vger.kernel.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 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).