From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Wilson Date: Sat, 14 Nov 2009 15:41:42 +0000 Subject: [ath9k-devel] ath9k: DMA failed to stop in 10 ms In-Reply-To: <20091113173507.GE3865@tux> References: <20091112152600.GA7562@sig21.net> <20091112181045.GA8839@sig21.net> <43e72e890911121013t7273c09fybff75fa2484cf07c@mail.gmail.com> <43e72e890911121014r13705ac0of8db341749bca528@mail.gmail.com> <20091112195437.GA11611@sig21.net> <50d9f33a0911130822y16e94817q42166bb69499e91@mail.gmail.com> <20091113173507.GE3865@tux> Message-ID: <50d9f33a0911140741o2fb5e2f0x34ae4842ddc4867c@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 2009/11/13 Luis R. Rodriguez : > I'll see if I can get compat-wireless tested to enable debug if you > don't want to compile wireless-testing. I've brought up compat-wireless synced to today's wireless-testing to try out the new drivers. I'm not getting the DMA failures with that ath9k driver (srcversion: A274B26D86317453E48E6A4), but then the speeds the driver is syncing at are between 2.0 Mbit/sec and 11 Mbit/sec about six inches from a 40 Mhz 802.11n AP. But hey, it's working! I am seeing a pause in throughput now rather than a failure when the network is scanned. 64 bytes from 192.168.2.1: icmp_seq=762 ttl=64 time=1.95 ms 64 bytes from 192.168.2.1: icmp_seq=763 ttl=64 time=2.11 ms 64 bytes from 192.168.2.1: icmp_seq=764 ttl=64 time=4375 ms 64 bytes from 192.168.2.1: icmp_seq=765 ttl=64 time=3375 ms 64 bytes from 192.168.2.1: icmp_seq=766 ttl=64 time=2375 ms 64 bytes from 192.168.2.1: icmp_seq=767 ttl=64 time=1375 ms 64 bytes from 192.168.2.1: icmp_seq=768 ttl=64 time=357 ms 64 bytes from 192.168.2.1: icmp_seq=769 ttl=64 time=2.05 ms 64 bytes from 192.168.2.1: icmp_seq=770 ttl=64 time=2.24 ms The pauses can be replicated by executing: sudo iw dev wlan0 scan -- Neil Wilson