On 2012-11-19 19:33 -0000, Chaoxing Lin wrote linux-wireless@xxxxxxxxxxxxxx...: Hi all, i can confim this, "Failed to stop TX DMA!" steel exists in 802.11s and other modes too, i use many different cards but all ar9002 based. CL>Just FYI CL> CL>Kernel 3.6.7 change log says "This patch might fix crashes and "Failed to stop TX DMA!" messages." CL> CL>I tried it on Dell laptop with ar9390 radio. CL>Still, I got error message like below CL> CL>"ath: phy0: Failed to stop TX DMA, queues=0x005!" CL>"ath: phy0: Failed to stop TX DMA, queues=0x001!" CL> CL>I am testing 802.11s mesh on 802.11a channel 40, no HT enabled. CL> CL> CL>----------------------------- CL> CL>commit cd585fb70b89fb57f8dffb03a2a72c30f81f5da6 CL>Author: Felix Fietkau <nbd@xxxxxxxxxxx> CL>Date: Fri Oct 26 00:31:11 2012 +0200 CL> CL> ath9k: fix stale pointers potentially causing access to free'd skbs CL> CL> commit 8c6e30936a7893a85f6222084f0f26aceb81137a upstream. CL> CL> bf->bf_next is only while buffers are chained as part of an A-MPDU CL> in the tx queue. When a tid queue is flushed (e.g. on tearing down CL> an aggregation session), frames can be enqueued again as normal CL> transmission, without bf_next being cleared. This can lead to the CL> old pointer being dereferenced again later. CL> CL> This patch might fix crashes and "Failed to stop TX DMA!" messages. CL> CL> Signed-off-by: Felix Fietkau <nbd@xxxxxxxxxxx> CL> Signed-off-by: John W. Linville <linville@xxxxxxxxxxxxx> CL> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> CL>_______________________________________________ CL>ath9k-devel mailing list CL>ath9k-devel@xxxxxxxxxxxxxxx CL>https://lists.ath9k.org/mailman/listinfo/ath9k-devel CL> C уважением With Best Regards Георгиевский Юрий. Georgiewskiy Yuriy +7 4872 711666 +7 4872 711666 факс +7 4872 711143 fax +7 4872 711143 Компания ООО "Ай Ти Сервис" IT Service Ltd http://nkoort.ru http://nkoort.ru JID: GHhost@xxxxxxxxxx JID: GHhost@xxxxxxxxxx YG129-RIPE YG129-RIPE
