Return-path: Received: from mail-qa0-f48.google.com ([209.85.216.48]:54432 "EHLO mail-qa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751045AbaLCR00 (ORCPT ); Wed, 3 Dec 2014 12:26:26 -0500 Received: by mail-qa0-f48.google.com with SMTP id v10so10671981qac.21 for ; Wed, 03 Dec 2014 09:26:26 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1417563128.32003.8.camel@dcbw.local> <87h9xdl30j.fsf@kamboji.qca.qualcomm.com> <878uipl2dl.fsf@kamboji.qca.qualcomm.com> Date: Wed, 3 Dec 2014 11:26:25 -0600 Message-ID: (sfid-20141203_182630_848136_8A3A339B) Subject: Re: Laptop disassociating by local choice (reason=17) From: Brent Taylor To: Kalle Valo Cc: linux-wireless , Dan Williams , Krishna Chaitanya , ath6kl@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Dec 3, 2014 at 10:58 AM, Brent Taylor wrote: > On Wed, Dec 3, 2014 at 8:05 AM, Brent Taylor wrote: >> On Tue, Dec 2, 2014 at 11:37 PM, Kalle Valo wrote: >>> Brent Taylor writes: >>> >>>> On Dec 2, 2014 11:24 PM, "Kalle Valo" wrote: >>>>> >>>>> Brent Taylor writes: >>>>> >>>>> > I actually ran the wpa_supplicant with -ddddt as the parameter not >>>>> > knowing how many 'd's I could put there before I hit the limit of the >>>>> > debugging. The wpa_supplicant on the ubuntu laptop is v0.7.3. I'll >>>>> > change the -ddddt to just -dddt and re-run the test again. >>>>> >>>>> IMHO 0.7.3 is ancient. Please use something more recent. >>>> >>>> Ancient it may be, but why would it work with the ath9k chip and not >>>> the ath6kl chip? >>> >>> Because of a bug we are not aware of? ath6kl and ath9k are very >>> different drivers and 0.7.3 might have some problem which only comes >>> with ath6kl. Up to you, but I would not waste time testing on that old >>> wpasupplicant. >>> >>> -- >>> Kalle Valo >> >> Apologies for my last reply not making it through the mailing lists, I >> sent it from my phone and it was automatically formatted in HTML and >> not Plain Text. >> >> The ultimate goal is to use an Android device to communicate with my >> custom device being the Access Point. The laptop is easier to debug >> (at the moment) than an Android device. I'm currently using a Samsung >> S4 running 4.4.4 and it was not able to complete the authentication >> step either. This is when I turned to using the laptop. Any idea >> what version of the wpa_supplicant is running on Kit Kat? >> >> -- Brent Taylor > > > Here is another log capture from the device and the laptop. This time > both were using -dddt as the debug parameter to wpa_supplicant. > > Laptop wpa_supplicant Log > -- snip last log data from 2014-12-03 -- I just found out that the Samsung S4 that we are testing with has wpa_supplicant version v2.0-devel-4.2.2 which is not KitKat, but Jelly Bean. Does anyone know if the logging can be turned on without rooting the phone? -- Brent Taylor