From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1WvSYs-0006BU-6V for ath10k@lists.infradead.org; Fri, 13 Jun 2014 14:34:34 +0000 Message-ID: <539B0BDF.30105@candelatech.com> Date: Fri, 13 Jun 2014 07:34:07 -0700 From: Ben Greear MIME-Version: 1.0 Subject: Re: RE : ath10k: firmware crash in station mode & problem DFS References: <1399565896-29791-1-git-send-email-greearb@candelatech.com> <538CAACA.2030202@candelatech.com> , <538E9D26.4040009@candelatech.com> , <538F9255.1060101@candelatech.com> , <5390A9CC.7060400@candelatech.com> , <5391E363.50907@candelatech.com> , <53972984.8020303@candelatech.com> , <53988C53.6030806@candelatech.com> , <539A0C06.6050105@candelatech.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Vu Hai NGUYEN Cc: Janusz Dziedzic , Patrick CARNEIRO RODRIGUEZ , "ath10k@lists.infradead.org" , Janusz Dziedzic On 06/13/2014 01:50 AM, Vu Hai NGUYEN wrote: >> I put a new series of patches (one build for every commit in my tree) >> here. This has the scan fix in place (at around build 70 or so) >> so hopefully a bisect will work OK for you. >> >> http://www.candelatech.com/downloads/ath10k-fw-all-images/ >> >> If you bisect the problem, please let me know the results >> and I'll try to track down the problem. > > Thanks, the different is between the 61th and 62th commit. I have to type "iw wlan0 scan" for the 62th commit firmware to connect after running wpa_supp. > They all had: > wlan0: CTRL-EVENT-SCAN-STARTED > wlan0: SME: Trying to authenticate with 04:f0:21:0e:38:be (SSID='ath10k' freq=5280 MHz) > wlan0: authenticate with 04:f0:21:0e:38:be > wlan0: direct probe to 04:f0:21:0e:38:be (try 1/3) > wlan0: direct probe to 04:f0:21:0e:38:be (try 2/3) > wlan0: direct probe to 04:f0:21:0e:38:be (try 3/3) > wlan0: authentication with 04:f0:21:0e:38:be timed out You see this with official firmware as well? Any idea why AP does not answer? > But the first firmware continue to do this: > wlan0: SME: Trying to authenticate with 04:f0:21:0e:38:be (SSID='ath10k' freq=5280 MHz) > wlan0: authenticate with 04:f0:21:0e:38:be > wlan0: authenticated > wlan0: Trying to associate with 04:f0:21:0e:38:be (try 1/3) > wlan0: associate with 04:f0:21:0e:38:be > wlan0: associated > > While the second one keeps saying: > wlan0: CTRL-EVENT-SCAN-STARTED I'll investigate the firmware change between 61 and 62, thanks for narrowing it down. Also, do you see this same behaviour on non-DFS channels? Thanks, Ben > > Thanks, > NGUYEN Vu Hai > Acita-Sodielec > Route de Mayres - B.P. 9 > 12100 St GEORGES DE LUZENCON > FRANCE > > > > _______________________________________________ > 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