From: Robbie Smith <zoqaeski@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Recurring “Failed to stop TX DMA” error
Date: Sat, 22 Jun 2013 14:47:25 +1000 [thread overview]
Message-ID: <51C52C5D.8010502@gmail.com> (raw)
In-Reply-To: <20928.34611.482103.288876@gargle.gargle.HOWL>
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.
next prev parent reply other threads:[~2013-06-22 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-06-22 5:52 ` Sujith Manoharan
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 17:23 Alexander Szlezak
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=51C52C5D.8010502@gmail.com \
--to=zoqaeski@gmail.com \
--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.