From: Howard Chu <hyc@symas.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: compat-wireless-2009-08-13 ath9k timeouts
Date: Thu, 13 Aug 2009 20:03:00 -0700 [thread overview]
Message-ID: <4A84D3E4.5050406@symas.com> (raw)
I just built this on my 2.6.31-rc5 kernel. Using the driver results in a flood of
[ 78.598403] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.599508] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.600500] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.600833] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.600833] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.600833] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
[ 78.601378] ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
in dmesg, and throughput is extremely slow. Surprising that there are multiple
messages in a single time tick.
I also tried with the ath9k driver from wireless-testing, as of commit
3fbf09eb3916 and got the same result.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
next reply other threads:[~2009-08-14 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 3:03 Howard Chu [this message]
2009-08-14 11:43 ` compat-wireless-2009-08-13 ath9k timeouts Howard Chu
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=4A84D3E4.5050406@symas.com \
--to=hyc@symas.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 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).