From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.candelatech.com ([208.74.158.172] helo=ns3.lanforge.com) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WQiYw-0004uK-AY for ath10k@lists.infradead.org; Thu, 20 Mar 2014 19:23:35 +0000 Message-ID: <532B4017.7060803@candelatech.com> Date: Thu, 20 Mar 2014 12:23:03 -0700 From: Ben Greear MIME-Version: 1.0 Subject: Re: Trouble connecting to broadcom AC APs? References: <5329CD60.6080609@candelatech.com> <87txatfkad.fsf@kamboji.qca.qualcomm.com> <532B104A.7060302@candelatech.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Adrian Chadd Cc: Kalle Valo , ath10k On 03/20/2014 12:17 PM, Adrian Chadd wrote: > Did the per-rate transmit statistics ever make it into the firmware / driver? > > I'd start by looking at what rate(s) it's trying and what the transmit > completion statistics say. It could be doing something exceedingly > dumb like transmitting on an invalid rate or stream setup. > > Same deal with STBC/LDPC. Try disabling those; see what happens. It appears the packets get to the AP, and AP at least tries to respond. If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too. Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air. Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs. Thanks, Ben > > > > -a > > > On 20 March 2014 08:59, Ben Greear wrote: >> On 03/19/2014 11:36 PM, Kalle Valo wrote: >>> Ben Greear writes: >>> >>>> We are seeing various funny things when trying to connect >>>> ath10k stations to commercial APs with broadcom AC NICs. >>>> >>>> It sort of works sometimes, but we often see failure to >>>> acquire DHCP lease in a timely manner, etc. >>> >>> So it's a problem with broadcast frames? With or without encryption? Did >>> you try disabling power save? >> >> With and without encryption we see issues. I am disabling power-save, >> but from poking around in firmware, I'm not sure how much affect that >> has. >> >> I'm using commands like this to disable it: >> ./local/sbin/iw dev sta219 set power_save off >> >>>> Similar testing on APs using QCA AC NICs appears to work >>>> much better. >>>> >>>> Our problems could be most anything, including the fact that this >>>> testing is done on our modified firmware, but I am curious if anyone >>>> else seems any similar issues? >>> >>> Occasionally I test connecting to D-Link DIR-865L in STA mode. But I >>> just do just simple ping tests and with manual IPs. >> >> We'll keep poking at things and see if we can find any >> pattern or work around. >> >> Thanks, >> Ben >> >> -- >> Ben Greear >> Candela Technologies Inc http://www.candelatech.com >> >> >> _______________________________________________ >> ath10k mailing list >> ath10k@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/ath10k -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k