On Tue, Feb 24, 2015 at 4:05 PM, Johannes Berg <johan...@sipsolutions.net> wrote: > On Tue, 2015-02-24 at 15:58 +0530, Krishna Chaitanya wrote: > >> STA (mac80211) connects to AP in VHT-80. >> AP is reconfigured to 11n40 (stops beaconing for about 30secs and then >> starts again). >> STA loses connection (HW_CONN_TRACK), iee80211_connection_loss is called. >> STA see's AP again and tries to connect, > > But this goes through the supplicant, right? You actually get a full > connection loss (which I certainly would expect after 30 seconds)
Our HW N/W lost event timeout is 5secs. >> but due to BW tracking in >> mac80211 it doesn't connect. >> >> So i guess we are not resetting the tracking after losing connection. > > Right, some flag is not getting reset correctly I suppose. I thought we > had pretty robust code for this, but I guess not. > > Easiest might be to print the flags and other state for during all > connection attempts, and then compare > * VHT connection > * subsequent HT connection > * HT connection after reloading the driver Sure Johannes, will share the info. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
