On Tue, 2015-05-05 at 12:22 -0700, Chirantan Ekbote wrote: > On Tue, May 5, 2015 at 3:46 AM, Bastien Nocera <had...@hadess.net> > wrote: > > > > > The last thing the power manager does, right before > > > writing "mem" to /sys/power/state, is write the wakeup_count > > > that it > > > read earlier to /sys/power/wakeup_count. If the write fails, the > > > power manager considers the suspend attempt failed, reads the new > > > wakeup_count, and starts a timer (usually 10 seconds) to retry > > > the > > > suspend. The same thing happens if the write to /sys/power/state > > > fails. > > > > Is this something that logind should do as well? > > > > We do it to avoid a race condition where a wakeup event occurs after > userspace has started the suspend process but before anything writes > "mem" to /sys/power/state. I'm guessing that this is something > logind > should be doing as well since the chances of missing a wakeup event > increase the longer any given delay inhibitor takes to delay a > suspend.
File https://bugzilla.freedesktop.org/show_bug.cgi?id=90339 Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
