On Tue, 06 Jan 2009 18:14:41 +0100, Johannes Berg wrote > > However, _with_ the current procedure of telling NM to go to sleep, it > > tries to reconnect after resume because NM takes care of downing the > > interfaces. As a result mac80211 never gets the chance to save the > > state of the running interfaces. > > You mean restore? > > Does that mean there's a race condition now, between userspace config > and the resume stuff? Can't we fix that by taking the rtnl? No, I mean that with dbus telling NM to go to sleep (as part of pm-utils) NM then takes down the interfaces -- userspace is still running, this is before the kernel actually suspends. Consequently, all the interfaces look down to mac80211 when suspend() is actually called so the suspend/resume in mac80211 doesn't wind up doing anything with interfaces. No race condition, but a re-association must happen from userspace on the resume side (NM will do this, though). At least this appears the case on f10, correct me if I'm wrong, Dan. -- Bob Copeland %% www.bobcopeland.com -- 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
