Return-path: Received: from s3.sipsolutions.net ([144.76.63.242]:37876 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753489AbdJQPKv (ORCPT ); Tue, 17 Oct 2017 11:10:51 -0400 Message-ID: <1508253043.10607.89.camel@sipsolutions.net> (sfid-20171017_171054_522281_7DD3AD68) Subject: Re: Commit 0711d638 breaks mwifiex From: Johannes Berg To: Jesse Sung Cc: Amitkumar Karwar , Nishant Sarmukadam , Ilan Peer , Anthony Wong , Jason Yen , Terry.Wey@dell.com, linux-wireless@vger.kernel.org Date: Tue, 17 Oct 2017 17:10:43 +0200 In-Reply-To: References: <1508233890.10607.70.camel@sipsolutions.net> <1508237298.10607.76.camel@sipsolutions.net> <1508246019.10607.77.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, > > > https://p.sipsolutions.net/8f9d5917a5cbe4b3.txt > > > > > > Can you also give that a spin? Thanks for testing! > > Issued four reassociate, the network interface is still alive. Also > > with this patch it stays with BSSID1 and I don't see any > > "Association request to the driver failed" in the process. > > Correction: I can still see "Association request to the driver > failed" and switching between BSSIDs with more reassociates but I > think that shouldn't be an issue? Not sure what you mean by "with more reassociates"? In any case, we suspect that there's another underlying issue in mwifiex, which happens to tickle this problem. Could you record a full trace with -e cfg80211 for me (and send it privately, please compress trace.dat e.g. with xz, it compresses really well) Thanks, johannes