From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
Linux-wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.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: Tue, 20 Mar 2012 10:42:03 -0700 [thread overview]
Message-ID: <4F68C16B.1090707@gmail.com> (raw)
In-Reply-To: <20328.41155.468698.30887@gargle.gargle.HOWL>
On 03/20/2012 08:22 AM, Sujith Manoharan wrote:
> Justin P. Mattock wrote:
>> both mohammed and sujith Thank you for the patches for this issue!
>> I really appreciate this..
>>
>> I went and applied the debug printk and added ath_node_attach as well to
>> my linux-next clone, will run for a few days to see if I get anything..
>> full dmesg is here..: http://fpaste.org/jHSX/
>
> Thanks for testing and please report if the issue is fixed.
>
> Sujith
>
no worries.. hopefully we can get this bug fixed.. will continue running
these patches and will send out anything I see..
Justin P. Mattock
next prev parent reply other threads:[~2012-03-20 17:42 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
[not found] ` <4F577D9B.7020402-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-03-07 17:27 ` Felix Fietkau
2012-03-07 17:37 ` Justin P. Mattock
[not found] ` <4F579A88.6030503-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
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
2012-03-19 16:09 ` Justin P. Mattock
[not found] ` <4F6751B2.1030809-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
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
[not found] ` <CAD2nsn2b9yVrX16m4Pc0F96PHF09ySv8ncY8Qnr7_9CC8hrbtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-25 15:05 ` Justin P. Mattock
[not found] ` <4F682555.3020502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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 [this message]
2012-03-25 23:00 ` Justin P. Mattock
[not found] ` <4F6FA388.9080408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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=4F68C16B.1090707@gmail.com \
--to=justinmattock@gmail.com \
--cc=c_manoha@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).