|author||Victor Lowther <firstname.lastname@example.org>||2008-11-28 16:15:15 -0600|
|committer||Victor Lowther <email@example.com>||2008-11-30 18:21:02 -0600|
90clock takes over a second to run on suspend.
Most systems do not need it. Add NEED_CLOCK_SYNC, and only run hwclock if it is set. This will probably go away entirely in a later release.
Diffstat (limited to 'README.debugging')
1 files changed, 6 insertions, 0 deletions
diff --git a/README.debugging b/README.debugging
index 76be415..47c756a 100644
@@ -21,6 +21,12 @@ End-user customization and debugging:
environment variable to have that module removed when the system
suspends and reloaded when the system wakes up.
+* If your clock drifts across a sleep/wake cycle, you can use
+ NEED_CLOCK_SYNC="true" to force pm-utils to synchronize clocks.
+ This is a change in the default behaviour of pm-utils -- 22.214.171.124 and earlier
+ always synchronized clocks, but doing so is slow and most hardware stays in
+ sync without assistance.
* To find out what parameters can be passed to pm-suspend and friends, run them
with '--help' as the first parameter as root. This will print out the
options that it supports and which hooks or modules handle those options.