From: Felix Fietkau <nbd@openwrt.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
Linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Linux-netdev <netdev@vger.kernel.org>
Subject: Re: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040
Date: Mon, 19 Mar 2012 16:33:06 +0100 [thread overview]
Message-ID: <4F6751B2.1030809@openwrt.org> (raw)
In-Reply-To: <4F674FF5.2060406@gmail.com>
On 2012-03-19 4:25 PM, Justin P. Mattock wrote:
> On 03/19/2012 08:20 AM, Mohammed Shafi wrote:
>> Hi Justin,
>>
>>> seems I got this when waking up from suspend, was trying to connect with NM
>>> then all of a sudden Xorg shut off and this appeared on the screen(image
>>> links below I could not save dmesg only pic)
>>> http://flic.kr/p/bEhf2K
>>> http://flic.kr/p/bEhf2x
>>> http://flic.kr/p/bEhf2n
>>> http://flic.kr/p/bEhf26
>>>
>>> I see ath9k in the image, but am unsure if its related.
>>> kernel is: 3.3.0-rc7-next-20120316
>>
>> this looks like some new issue in ath9k, lets try to recreate it here
>>
>>>
>>> Justin P. Mattock
>>>
>>>
>>>
>>
>>
>>
>
> would be nice to recreate, then bisecting will be more accurate to do..
> I am trying userspace tweaks here and there but no luck(hostapd etc..)
> keep in mind this is for the RX DMA, the above just occured..
> as for writing a small app I still need to try, but my C skills only go
> so far(anything to trigger!).
Was your kernel compiled with debug info? If so, please run gdb on the
ath9k.ko module and enter this:
l *ath9k_tx+start+0x284
Then send me the output of that.
- Felix
next prev parent reply other threads:[~2012-03-19 15:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 14:25 ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040 Justin P. Mattock
2012-03-07 15:19 ` Mohammed Shafi
2012-03-07 15:24 ` Justin P. Mattock
2012-03-07 17:27 ` Felix Fietkau
2012-03-07 17:37 ` Justin P. Mattock
2012-03-08 21:18 ` Justin P. Mattock
2012-03-15 13:57 ` Justin P. Mattock
2012-03-16 19:45 ` Justin P. Mattock
2012-03-19 14:43 ` Justin P. Mattock
2012-03-19 15:20 ` Mohammed Shafi
2012-03-19 15:25 ` Justin P. Mattock
2012-03-19 15:33 ` Felix Fietkau [this message]
2012-03-19 16:09 ` Justin P. Mattock
2012-03-20 5:54 ` Justin P. Mattock
2012-03-20 6:19 ` Mohammed Shafi
2012-03-20 6:27 ` Justin P. Mattock
2012-03-20 6:32 ` Mohammed Shafi
2012-03-20 6:36 ` Justin P. Mattock
2012-03-20 7:44 ` Mohammed Shafi
2012-03-25 15:05 ` Justin P. Mattock
2012-03-20 8:29 ` Sujith Manoharan
2012-03-20 9:37 ` Mohammed Shafi
2012-03-20 11:15 ` Mohammed Shafi
2012-03-20 11:36 ` Mohammed Shafi
2012-03-20 11:46 ` Mohammed Shafi
2012-03-20 14:19 ` Justin P. Mattock
2012-03-20 15:22 ` Sujith Manoharan
2012-03-20 17:42 ` Justin P. Mattock
2012-03-25 23:00 ` Justin P. Mattock
2012-03-27 2:17 ` Sujith Manoharan
2012-04-06 16:40 ` Justin P. Mattock
2012-04-06 16:56 ` 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=4F6751B2.1030809@openwrt.org \
--to=nbd@openwrt.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).