On Tue, 2013-01-01 at 12:06 -0600, Larry Finger wrote: > > [ 436.155998] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3) > > [ 436.158343] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 > > status=0 aid=4) [ 436.158478] wlan0: associated [ 436.158538] IPv6: > > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 446.153705] > > ------------[ cut here ]------------ [ 446.153765] WARNING: at > > net/wireless/mlme.c:517 cfg80211_mlme_disassoc+0x17d/0x190 [cfg80211]() > > This one indicates that there was a call to disassociate when the device was not > associated. It might have been informative to have seen the logged messages > earlier than 436.155474 seconds. > > Johannes: Why is this a WARN_ON condition? Certainly, the returned -ENOTCON does > the right thing, even though some part of the system got confused. That's why it's a warning, it points to an internal state confusion -- current_bss should always be assigned if sme_state is SME_CONNECTED. Or so I thought, evidently that's not the case. I don't see how this happens in the code though. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
