From: "Kim Lidström" <dexter@lacto.se>
To: Mohammed Shafi <shafi.wireless@gmail.com>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
Adrian Chadd <adrian@freebsd.org>
Subject: Re: "Failed to stop Tx DMA" and "Could not stop RX" with AR9485
Date: Thu, 01 Mar 2012 06:53:37 +0100 [thread overview]
Message-ID: <4F4F0EE1.2020202@lacto.se> (raw)
In-Reply-To: <CAD2nsn2ifGDPr_J7LtBS04yCkxg12jQShrCDCBUERmOC5kodyA@mail.gmail.com>
On 03/01/2012 06:09 AM, Mohammed Shafi wrote:
>> With this message I have attached a log with the error messages.
>> This has been a problem since.. Uhm.. Kernel 3.2.something and I'm
>> currently running 3.2.8.
>> For some reason it happened at least 3-4 times shortly after each other
>> today - so I thought I might ask on here what's happening.
>
> disabling power save would be a nice idea, to see if this issue disappears.
> i got the same issue after a long stress test with some other card, sujith
> gave me the idea to see if disabling PS helps
> sudo iwconfig wlanX power off
> sudo iw dev wlanX set power_save off
> also please ensure that you run with your power adapter :) i noticed
> PS gets enabled
> via wext when we plug out the power adapter
>
I just tried it and will see what happens! That might take a while,
though, because it seems to occur at random.
But you know something? The thought has struck me before that it might
have something to do with power saving. Interesting :)
next prev parent reply other threads:[~2012-03-01 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:35 "Failed to stop Tx DMA" and "Could not stop RX" with AR9485 Kim Lidström
2012-02-29 21:50 ` Adrian Chadd
2012-02-29 23:52 ` Adrian Chadd
2012-03-01 5:09 ` Mohammed Shafi
2012-03-01 5:53 ` Kim Lidström [this message]
2012-03-07 17:29 ` [ath9k-devel] " Felix Fietkau
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=4F4F0EE1.2020202@lacto.se \
--to=dexter@lacto.se \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.com \
/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).