All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Schmidt <bschmidt@techwires.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] DMA issues with ar9280 cards
Date: Fri, 4 Mar 2011 12:29:22 +0100	[thread overview]
Message-ID: <201103041229.23195.bschmidt@techwires.net> (raw)
In-Reply-To: <AANLkTik2b5dkTXXs-r4ww5C5M3iz+bWAtAebGfqvcsoH@mail.gmail.com>

On Wednesday, March 02, 2011 15:51:37 Mohammed Shafi wrote:
> On Thu, Feb 24, 2011 at 1:36 AM, Bernhard Schmidt
> <bschmidt@techwires.net> wrote:
> > On Wednesday 23 February 2011 18:46:49 Luis R. Rodriguez wrote:
> >> On Wed, Feb 23, 2011 at 12:55:35AM -0800, Bernhard Schmidt wrote:
> >> > % scan done, setting up the BSS
> >> > [  296.060536] ath: Failed to stop TX DMA in 100 msec after killing last frame
> >> > [  296.075985] ath: Failed to stop TX DMA in 100 msec after killing last frame
> >> > [  296.083032] ath: Failed to stop TX DMA!
> >> > [  296.099187] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
> >> > [  296.106884] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
> >> > [  296.127247] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
> >> > [  297.163998] ath: Failed to stop TX DMA in 100 msec after killing last frame
> >> > [  297.182977] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
> >> > [  297.190677] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
> >> > [  297.211004] ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
> >> > [  298.247659] ath: Failed to stop TX DMA in 100 msec after killing last frame
> >> > % ..
> >>
> >> If its so easy to reproduce we can likely fix this for good!
> >
> > Actually, haven't found a way to *not* reproduce it. :)
> 
> the obvious way of increasing the timeout for stopping the DMA might help ?
> in mac.c
> 
> 148 #define ATH9K_TX_STOP_DMA_TIMEOUT       4000    /* usec */
> increase it to 10000 usec
> 
> and
> 781#define AH_RX_STOP_DMA_TIMEOUT 10000   /* usec */
> increase it to 20,000 usec

Did try to play with various values, no differences whatsoever,
obviously. Even tried polling a whole second. The messages do indicate
that there is an issue. It's not that the reg isn't polled for long
enough, but instead this is an indicator for something wrong going on.
What I'm wondering though is, that the queue resets which eventually
happen do not have any effect, only after a "full" reset (e.g.
ifconfig down/up) the queues will be usable again.

On a site note, after falling back to other chips (9380, 9160), I see
the same issue there too. Not as often, or as immediate as with 9280,
but they do occur (even on different hardware). Having a hostapd
instance idle long enough is able to trigger it eventually.

-- 
Bernhard

  reply	other threads:[~2011-03-04 11:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201102230955.35674.bschmidt@techwires.net>
2011-02-23 17:46 ` [ath9k-devel] DMA issues with ar9280 cards Luis R. Rodriguez
2011-02-23 18:12   ` Adrian Chadd
2011-02-23 18:20     ` Adrian Chadd
2011-02-23 18:24       ` Jouni Malinen
2011-02-23 18:40         ` Adrian Chadd
2011-02-23 23:06           ` Jouni Malinen
2011-02-23 20:06   ` Bernhard Schmidt
2011-02-24  9:33     ` Bernhard Schmidt
2011-02-24 18:18       ` Luis R. Rodriguez
2011-02-25  9:37         ` Bernhard Schmidt
2011-02-25 17:12           ` Luis R. Rodriguez
2011-02-26  9:37             ` Bernhard Schmidt
2011-03-10  0:40               ` Felix Fietkau
2011-03-02 14:51     ` Mohammed Shafi
2011-03-04 11:29       ` Bernhard Schmidt [this message]
2011-03-04 15:25         ` Mohammed Shafi
2011-03-04 15:29           ` Mohammed Shafi
2011-03-04 17:16             ` Bernhard Schmidt
2011-03-09  9:58               ` Mohammed Shafi
2011-03-09 10:01               ` Mohammed Shafi
2011-03-05 23:49         ` crocket
2011-03-09 10:22           ` Peter Stuge
2011-02-23 15:34 Bernhard Schmidt
2011-02-23 16:22 ` Peter Stuge
2011-02-23 18:02   ` Luis R. Rodriguez
2011-02-23 19:51     ` Peter Stuge

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=201103041229.23195.bschmidt@techwires.net \
    --to=bschmidt@techwires.net \
    --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.