[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikPQt+njjFPB6sJ-mEcsx6f-R6TAOhEd8egkqhH@mail.gmail.com>
Date: Tue, 8 Mar 2011 14:45:02 -0500
From: Brian Prodoehl <bprodoehl@...il.com>
To: Ben Greear <greearb@...delatech.com>
Cc: "Justin P. Mattock" <justinmattock@...il.com>,
Mohammed Shafi <shafi.wireless@...il.com>,
"John W. Linville" <linville@...driver.com>,
linux-wireless@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ath9k-devel@...eros.com
Subject: Re: WARNING: at drivers/net/wireless/ath/ath9k/recv.c:536
ath_stoprecv+0xc8/0xda [ath9k]()
On Tue, Mar 8, 2011 at 2:27 PM, Ben Greear <greearb@...delatech.com> wrote:
> On 03/08/2011 10:49 AM, Justin P. Mattock wrote:
>>
>> On 03/07/2011 07:22 AM, Mohammed Shafi wrote:
>>>
>>> On Mon, Mar 7, 2011 at 8:42 PM, John W.
>>> Linville<linville@...driver.com> wrote:
>>>>
>>>> On Sun, Mar 06, 2011 at 12:47:05AM -0800, Justin Mattock wrote:
>>>>
>>>>> full dmesg here:
>>>>> http://fpaste.org/5JQp/
>>>>> let me know if I need to supply any info(also I can try a bisect, but
>>>>> am in the middle of changing residencies, so it might not be right
>>>>> away)
>>>>
>>>> One of the Atheros guys suggested that you change a DMA timeout value.
>>>> Did you try that?
>>>
>>> John it looks like increasing the timeout also does not seems to help.
>>> A user reported this issue in ath9k developer list and he told that
>>> increasing the timeout did not fix this issue.
>>>
>>>>
>>>> John
>>>> --
>>>> John W. Linville Someday the world will need a hero, and you
>>>> linville@...driver.com might be all we have. Be ready.
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> linux-wireless" in
>>>> the body of a message to majordomo@...r.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>
>> at barnes and noble, and I see this has fired off again. will see if I
>> can reproduce and bisect.
>
> This problem goes way back, and the driver has had lots of fixes in the
> last few months, so I'm not sure if bisecting is going to
> do you any good.
>
> Thanks,
> Ben
The warnings have been around since you added the check for the
problem, right? I remember initially it was a WARN_ON, and I'd get a
steady flood of backtraces, and then it was switched to a
WARN_ON_ONCE. I see these on every platform I have (x86_64, IXP425
and AR71xx) with AR9002 and AR9003.
-Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists