diff options
| author | Pavel Machek <pavel@ucw.cz> | 2015-01-26 14:43:04 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-01-30 01:29:46 +0100 |
| commit | a03ff6f20c396fb84cf61501a31fefdf0a5eb5a7 (patch) | |
| tree | 92fc39aab529603357b5c7aa26b9bc55fa35a5e7 | |
| parent | d78cb3680c8e95c100d5a351b8cfc7dd3c589b68 (diff) | |
PM / sleep: Mention async suspend in PM_TRACE documentation
Document pm_tracing actually affecting suspend in non-trivial way.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
| -rw-r--r-- | Documentation/power/s2ram.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/power/s2ram.txt b/Documentation/power/s2ram.txt index 1bdfa044377..4685aee197f 100644 --- a/Documentation/power/s2ram.txt +++ b/Documentation/power/s2ram.txt @@ -69,6 +69,10 @@ Reason for this is that the RTC is the only reliably available piece of hardware during resume operations where a value can be set that will survive a reboot. +pm_trace is not compatible with asynchronous suspend, so it turns +asynchronous suspend off (which may work around timing or +ordering-sensitive bugs). + Consequence is that after a resume (even if it is successful) your system clock will have a value corresponding to the magic number instead of the correct date/time! It is therefore advisable to use a program like ntp-date |