Red Hat Bugzilla – Bug 59994
Laptop resume does not respect clock's UTC=false
Last modified: 2007-04-18 12:40:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205
Description of problem:
On resume from suspend-to-memory (at least on my Dell CPxJ and C610),
the clock will sometimes be set to five hours behind the hardware clock.
Coincidentally, this is the difference between my timezone and UTC. My hardware
clock is local time, so the system clock ends up five hours behind.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set UTC=false in /etc/sysconfig/clock, and set hwclock to local time.
2. Suspend laptop.
3. Resuem laptop.
Actual Results: Sometimes system clock is set to local time minus five hours
Expected Results: Clock should always resume to hwclock time if UTC=false.
If you don't catch this and shut down the machine with the clock set
incorrectly, then the hwclock is synced to the wrong time. On next startup, the
system clock will be set correctly to the incorrect hwclock time. This behavior
might have been reported as another bug some time in the past.
That's caused by a behavior change in hwclock - older versions would always assume
--localtime if --utc wasn't specified.
Current versions use whatever was used before if neither is specified.
I've adapted apmscript in apmd 3.0.2-6.
*** Bug 7062 has been marked as a duplicate of this bug. ***