Re: ath: DMA failed to stop in 10 ms AR_CR=0x00000024AR_DIAG_SW=0x02000020 DMADBG_7=0x00008040

[Mohammed Shafi]

On Tue, Mar 20, 2012 at 11:57 AM, Justin P. Mattock
<justinmattock@xxxxxxxxx> wrote:
> On 03/19/2012 11:19 PM, Mohammed Shafi wrote:
>>>
>>> (gdb) list *ath9k_tx+start+0x284
>>> No symbol "start" in current context.
>>
>>
>> hey, pls try l *(ath9k_tx_start+0x284), yesterday i did the same in
>> the latest wireless testing tree it pointed to line 1929 of xmit.c
>>
>> sc->tx.seq_no +=0x10;
>>
>> also did few suspend/resume in my machine, nothing interesting happened
>>
>>>
>>> before receiving the email to do the above code with gdb I had cleaned
>>> the
>>> tree out with git clean -fx so rebuilding might have misalighned
>>> things(but
>>> could be wrong)..
>>>
>>
>>
>>
>
>
> seems gdb is not working with that code but works if I remove _start.
> (maybe -next took this out or something)
>
> (gdb) l *(ath9k_tx_start+0x284)
> No symbol "ath9k_tx_start" in current context.

sorry its
 l *(ath_tx_start+0x284)

> (gdb) l *(ath9k_tx+0x284)
> 0x4854 is in ath_paprd_activate (drivers/net/wireless/ath/ath9k/main.c:395).
> 390                             continue;
> 391
> 392                     ar9003_paprd_populate_single_table(ah, caldata,
> chain);
> 393             }
> 394
> 395             ar9003_paprd_enable(ah, true);
> 396             ath9k_ps_restore(sc);
> 397     }
> 398
> 399     static bool ath_paprd_send_frame(struct ath_softc *sc, struct
> sk_buff *skb, int chain)
>
> right now I am running next, will wait for the RX DMA to get a clean trace,
> then will look to see.. as for the other issue I just rebooted and hit this
> during bootup.
>
> Justin P. Mattock



-- 
thanks,
shafi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/