From: Felix Fietkau <nbd@openwrt.org>
To: "Kim Lidström" <dexter@lacto.se>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] "Failed to stop Tx DMA" and "Could not stop RX" with AR9485
Date: Wed, 07 Mar 2012 18:29:56 +0100 [thread overview]
Message-ID: <4F579B14.4020109@openwrt.org> (raw)
In-Reply-To: <4F4E9A36.2080809@lacto.se>
On 2012-02-29 10:35 PM, Kim Lidström wrote:
> Hello!
> A while ago I had a situation where my AR9485 would lock up the kernel
> so bad and two very nice guys(Mohammed Shafi and Adrian.. Uhm.. Sorry I
> forgot his last name) were very patient in helping me and trying to
> debug it through patches, etc. Nothing worked.
> Eventually, though, I noticed that when I removed the atl1c module my
> wlan started working. "Awesome!" I thought... Until I noticed this other
> problem.
>
> Once in a while, seemingly at random, the wlan dies with the error
> messages in the title. And I can't possibly restore it without
> restarting the computer.
>
> 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.
Please try this patch with powersave enabled, using a recent
compat-wireless build (3.3 or linux-next based):
http://nbd.name/ps-fix.patch
- Felix
prev parent reply other threads:[~2012-03-07 17:29 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
2012-03-07 17:29 ` Felix Fietkau [this message]
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=4F579B14.4020109@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=dexter@lacto.se \
--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).