From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath9k: DMA error without scan optimization.
Date: Wed, 01 Dec 2010 10:58:05 -0800 [thread overview]
Message-ID: <4CF69ABD.1060204@candelatech.com> (raw)
As a work-around, I disabled the scan optimization by running one
wpa-supplicant per interface. This makes the system much more stable,
and it ran overnight with 30 STA interfaces at low speed (64kbps
tx + rx for each STA).
This morning, I bumped speed to 384Kbps, and it ran fine for 30
minutes or so. Then, I noticed this error on the console.
The system seems OK still, but I figure it's a matter of time.
Any suggestions for working around this error? Maybe try
stopping DMA several times in a loop?
sta7: detected beacon loss from AP - sending probe request
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
------------[ cut here ]------------
WARNING: at /home/greearb/git/linux.wireless-testing/drivers/net/wireless/ath/ath9k/recv.c:532 ath_stoprecv+0x90/0x9a [ath9k]()
Hardware name: PDSBM
Could not stop RX, we could be confusing the DMA engine when we start RX up
Modules linked in: michael_mic aes_i586 aes_generic 8021q garp stp llc macvlan pktgen fuse nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 uinput arc4 ecb
ath9k mac80211 ath9k_common ath9k_hw microcode ath e1000e cfg80211 iTCO_wdt iTCO_vendor_support pcspkr i2c_i801 i915 drm_kms_helper drm i2c_algo_bit i2c_core
video output [last unloaded: ipt_addrtype]
Pid: 24656, comm: kworker/u:2 Tainted: G W 2.6.37-rc3-wl+ #53
Call Trace:
[<78436fe9>] warn_slowpath_common+0x77/0x8c
[<f8f6c19e>] ? ath_stoprecv+0x90/0x9a [ath9k]
[<f8f6c19e>] ? ath_stoprecv+0x90/0x9a [ath9k]
[<7843707a>] warn_slowpath_fmt+0x2e/0x30
[<f8f6c19e>] ath_stoprecv+0x90/0x9a [ath9k]
[<f8f6a495>] ath_reset+0x55/0x163 [ath9k]
[<7844090e>] ? process_timeout+0x0/0xa
[<f8f6b9c9>] ath_hw_check+0x3f/0x4a [ath9k]
[<78447000>] process_one_work+0x1af/0x2bf
[<78446f8f>] ? process_one_work+0x13e/0x2bf
[<f8f6b98a>] ? ath_hw_check+0x0/0x4a [ath9k]
[<7844874e>] worker_thread+0xf9/0x1bf
[<78448655>] ? worker_thread+0x0/0x1bf
[<7844b27e>] kthread+0x62/0x67
[<7844b21c>] ? kthread+0x0/0x67
[<784036c6>] kernel_thread_helper+0x6/0x1a
---[ end trace c9b5512870bdacf6 ]---
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2010-12-01 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CF69ABD.1060204@candelatech.com \
--to=greearb@candelatech.com \
--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 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.