All of lore.kernel.org
 help / color / mirror / Atom feed
* [ath9k-devel] Recurring “Failed to stop TX DMA” error
@ 2013-06-18 14:36 Robbie Smith
  2013-06-18 16:13 ` Sujith Manoharan
  0 siblings, 1 reply; 5+ messages in thread
From: Robbie Smith @ 2013-06-18 14:36 UTC (permalink / raw)
  To: ath9k-devel

Hello list

I?ve been having issues with the stability of my network connections 
using the ath9k driver. Connections will drop for no apparent reason, 
packets seem to get lost in transit, and streaming seems to hang. 
Checking my logs I get a whole lot of messages along the lines of the 
following:

> Jun 19 00:03:08 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
> Jun 19 00:03:39 gallifrey kernel: cfg80211: Calling CRDA to update world regulatory domain
> Jun 19 00:03:39 gallifrey kernel: cfg80211: World regulatory domain updated:
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211: Calling CRDA for country: AU
> Jun 19 00:03:39 gallifrey kernel: cfg80211: Regulatory domain changed to country: AU
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
> Jun 19 00:03:40 gallifrey kernel: wlan0: authenticate with c8:be:19:58:16:58
> Jun 19 00:03:40 gallifrey kernel: wlan0: send auth to c8:be:19:58:16:58 (try 1/3)
> Jun 19 00:03:40 gallifrey kernel: wlan0: authenticated
> Jun 19 00:03:40 gallifrey kernel: wlan0: associate with c8:be:19:58:16:58 (try 1/3)
> Jun 19 00:03:40 gallifrey kernel: wlan0: RX AssocResp from c8:be:19:58:16:58 (capab=0x411 status=0 aid=1)
> Jun 19 00:03:40 gallifrey kernel: wlan0: associated
> Jun 19 00:03:40 gallifrey kernel: cfg80211: Calling CRDA for country: AU
> Jun 19 00:03:40 gallifrey kernel: ath: regdomain 0x8024 updated by CountryIE
> Jun 19 00:03:40 gallifrey kernel: ath: EEPROM regdomain: 0x8024
> Jun 19 00:03:40 gallifrey kernel: ath: EEPROM indicates we should expect a country code
> Jun 19 00:03:40 gallifrey kernel: ath: doing EEPROM country->regdmn map search
> Jun 19 00:03:40 gallifrey kernel: ath: country maps to regdmn code: 0x21
> Jun 19 00:03:40 gallifrey kernel: ath: Country alpha2 being used: AU
> Jun 19 00:03:40 gallifrey kernel: ath: Regpair used: 0x21
> Jun 19 00:03:40 gallifrey kernel: cfg80211: Regulatory domain changed to country: AU
> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
> ?
> Jun 19 00:13:24 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
> Jun 19 00:13:39 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
> Jun 19 00:13:42 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
> Jun 19 00:13:43 gallifrey kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006100
> Jun 19 00:13:43 gallifrey kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

If I read that output correctly, I?m getting the infamous TX DMA bug, 
and for some reason the computer repeatedly attempts to reconnect to the 
network. This only occurs on WPA protected networks, mainly on the one 
in my residence, which I do not have administrative rights to.

I?ve got a Atheros AR9485 network card, and I?m currently running the 
3.9.6 kernel (x86_64) on Arch Linux, though this issue occurs on every 
3.x kernel I?ve tested. I?ve tried running the compat-drivers on older 
kernels, but I can?t compile it on the current release, nor have I had 
much success with the backports driver (are they the same release with 
different names?).

Is there any more information I could provide that might help pinpoint 
what is happening?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [ath9k-devel] Recurring “Failed to stop TX DMA” error
  2013-06-18 14:36 [ath9k-devel] Recurring “Failed to stop TX DMA” error Robbie Smith
@ 2013-06-18 16:13 ` Sujith Manoharan
  2013-06-22  4:47   ` Robbie Smith
  0 siblings, 1 reply; 5+ messages in thread
From: Sujith Manoharan @ 2013-06-18 16:13 UTC (permalink / raw)
  To: ath9k-devel

Robbie Smith wrote:
> I?ve got a Atheros AR9485 network card, and I?m currently running the 
> 3.9.6 kernel (x86_64) on Arch Linux, though this issue occurs on every 
> 3.x kernel I?ve tested. I?ve tried running the compat-drivers on older 
> kernels, but I can?t compile it on the current release, nor have I had 
> much success with the backports driver (are they the same release with 
> different names?).
> 
> Is there any more information I could provide that might help pinpoint 
> what is happening?

Various fixes for AR9485 have been posted, so it would be good to try
the wireless-testing kernel. The fixes are not in 3.9.x.

The latest backports release is a bit dated and doesn't contain the
AR9485 fixes from: https://bugzilla.kernel.org/show_bug.cgi?id=49201

Once a new backports release is made, it can be used.

Sujith

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [ath9k-devel] Recurring “Failed to stop TX DMA” error
@ 2013-06-18 17:23 Alexander Szlezak
  0 siblings, 0 replies; 5+ messages in thread
From: Alexander Szlezak @ 2013-06-18 17:23 UTC (permalink / raw)
  To: ath9k-devel

Hi Robbie,

I can confirm The error happening on our ar92x Ubnt devices too.

What I could Figuren out so far it is moore frequent in heavy traffic and if we operate too or moore VAPs oft which at least one is wpa2 encrypted.

I notes that having the wpa2 vap first improoves reliability Rover having an unencrypted vap first.

I can Providence some logs if necessary.

Best Alex


Robbie Smith <zoqaeski@gmail.com> schrieb:

>Hello list
>
>I?ve been having issues with the stability of my network connections 
>using the ath9k driver. Connections will drop for no apparent reason, 
>packets seem to get lost in transit, and streaming seems to hang. 
>Checking my logs I get a whole lot of messages along the lines of the 
>following:
>
>> Jun 19 00:03:08 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
>> Jun 19 00:03:39 gallifrey kernel: cfg80211: Calling CRDA to update world regulatory domain
>> Jun 19 00:03:39 gallifrey kernel: cfg80211: World regulatory domain updated:
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211: Calling CRDA for country: AU
>> Jun 19 00:03:39 gallifrey kernel: cfg80211: Regulatory domain changed to country: AU
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
>> Jun 19 00:03:39 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
>> Jun 19 00:03:40 gallifrey kernel: wlan0: authenticate with c8:be:19:58:16:58
>> Jun 19 00:03:40 gallifrey kernel: wlan0: send auth to c8:be:19:58:16:58 (try 1/3)
>> Jun 19 00:03:40 gallifrey kernel: wlan0: authenticated
>> Jun 19 00:03:40 gallifrey kernel: wlan0: associate with c8:be:19:58:16:58 (try 1/3)
>> Jun 19 00:03:40 gallifrey kernel: wlan0: RX AssocResp from c8:be:19:58:16:58 (capab=0x411 status=0 aid=1)
>> Jun 19 00:03:40 gallifrey kernel: wlan0: associated
>> Jun 19 00:03:40 gallifrey kernel: cfg80211: Calling CRDA for country: AU
>> Jun 19 00:03:40 gallifrey kernel: ath: regdomain 0x8024 updated by CountryIE
>> Jun 19 00:03:40 gallifrey kernel: ath: EEPROM regdomain: 0x8024
>> Jun 19 00:03:40 gallifrey kernel: ath: EEPROM indicates we should expect a country code
>> Jun 19 00:03:40 gallifrey kernel: ath: doing EEPROM country->regdmn map search
>> Jun 19 00:03:40 gallifrey kernel: ath: country maps to regdmn code: 0x21
>> Jun 19 00:03:40 gallifrey kernel: ath: Country alpha2 being used: AU
>> Jun 19 00:03:40 gallifrey kernel: ath: Regpair used: 0x21
>> Jun 19 00:03:40 gallifrey kernel: cfg80211: Regulatory domain changed to country: AU
>> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
>> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
>> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
>> Jun 19 00:03:40 gallifrey kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
>> ?
>> Jun 19 00:13:24 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
>> Jun 19 00:13:39 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
>> Jun 19 00:13:42 gallifrey kernel: ath: phy0: Failed to stop TX DMA, queues=0x004!
>> Jun 19 00:13:43 gallifrey kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006100
>> Jun 19 00:13:43 gallifrey kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
>
>If I read that output correctly, I?m getting the infamous TX DMA bug, 
>and for some reason the computer repeatedly attempts to reconnect to the 
>network. This only occurs on WPA protected networks, mainly on the one 
>in my residence, which I do not have administrative rights to.
>
>I?ve got a Atheros AR9485 network card, and I?m currently running the 
>3.9.6 kernel (x86_64) on Arch Linux, though this issue occurs on every 
>3.x kernel I?ve tested. I?ve tried running the compat-drivers on older 
>kernels, but I can?t compile it on the current release, nor have I had 
>much success with the backports driver (are they the same release with 
>different names?).
>
>Is there any more information I could provide that might help pinpoint 
>what is happening?
>_______________________________________________
>ath9k-devel mailing list
>ath9k-devel at lists.ath9k.org
>https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [ath9k-devel] Recurring “Failed to stop TX DMA” error
  2013-06-18 16:13 ` Sujith Manoharan
@ 2013-06-22  4:47   ` Robbie Smith
  2013-06-22  5:52     ` Sujith Manoharan
  0 siblings, 1 reply; 5+ messages in thread
From: Robbie Smith @ 2013-06-22  4:47 UTC (permalink / raw)
  To: ath9k-devel

On 19/06/13 02:13, Sujith Manoharan wrote:
> Robbie Smith wrote:
>> I?ve got a Atheros AR9485 network card, and I?m currently running the
>> 3.9.6 kernel (x86_64) on Arch Linux, though this issue occurs on every
>> 3.x kernel I?ve tested. I?ve tried running the compat-drivers on older
>> kernels, but I can?t compile it on the current release, nor have I had
>> much success with the backports driver (are they the same release with
>> different names?).
>>
>> Is there any more information I could provide that might help pinpoint
>> what is happening?
>
> Various fixes for AR9485 have been posted, so it would be good to try
> the wireless-testing kernel. The fixes are not in 3.9.x.
>
> The latest backports release is a bit dated and doesn't contain the
> AR9485 fixes from: https://bugzilla.kernel.org/show_bug.cgi?id=49201
>
> Once a new backports release is made, it can be used.
>
> Sujith
>
Is there a wireless-testing suite of just the networking modules, like a 
backports-git where I can get the latest fixes? I?d rather not 
potentially introduce all sorts of other complications (i.e. ATi 
Catalyst issues?the open-source drivers don?t work properly on my 
chipset) testing a new kernel, nor spend hours compiling new kernels as 
this is the only computer I have access to, so I need it to be 
[relatively] stable for work.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [ath9k-devel] Recurring “Failed to stop TX DMA” error
  2013-06-22  4:47   ` Robbie Smith
@ 2013-06-22  5:52     ` Sujith Manoharan
  0 siblings, 0 replies; 5+ messages in thread
From: Sujith Manoharan @ 2013-06-22  5:52 UTC (permalink / raw)
  To: ath9k-devel

Robbie Smith wrote:
> Is there a wireless-testing suite of just the networking modules, like a 
> backports-git where I can get the latest fixes? I?d rather not 
> potentially introduce all sorts of other complications (i.e. ATi 
> Catalyst issues?the open-source drivers don?t work properly on my 
> chipset) testing a new kernel, nor spend hours compiling new kernels as 
> this is the only computer I have access to, so I need it to be 
> [relatively] stable for work.

Well the backports project aims to do exactly that. :)
Specific subsystems can be selected or individual drivers.

https://git.kernel.org/cgit/linux/kernel/git/mcgrof/backports.git/

Sujith

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-06-22  5:52 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-18 14:36 [ath9k-devel] Recurring “Failed to stop TX DMA” error Robbie Smith
2013-06-18 16:13 ` Sujith Manoharan
2013-06-22  4:47   ` Robbie Smith
2013-06-22  5:52     ` Sujith Manoharan
  -- strict thread matches above, loose matches on Subject: below --
2013-06-18 17:23 Alexander Szlezak

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.