On Wed, 2013-05-08 at 09:18 -0700, Ben Greear wrote: > Ok, I reproduced this with yet more debugging printouts in the kernel. > > The symptom is this: > > The sme_state is SME_CONNECTED, so it bails out below before sending the > 'connected' message to user-space. Is your system being really really really slow and/or are threads getting pre-empted a lot? This maybe seem like a bit of a stretch, but it seems possible that this happens: ieee80211_sta_rx_queued_mgmt() is running, possibly on one CPU, and is somewhere between printing "associated" and calling cfg80211_send_rx_assoc() (or in the call already, before taking the lock though.) Then your interface is set down at the same time, possibly on a different CPU. Here's where the scenario gets stretched, clearly your interface is getting set down over a minute later, I don't see how you could have stalled the other thread for that long. But if you did, then that thread is still processing things while the interface is going down, cfg80211 didn't know anything about the association having completed so it won't have disconnected, etc. So far, I haven't found any other scenario, nor a solution. 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
