Bug 802819 - hardware clock not set on hibernate
hardware clock not set on hibernate
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: pm-utils (Show other bugs)
16
All Linux
unspecified Severity low
: ---
: ---
Assigned To: Jaroslav Škarvada
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-13 10:53 EDT by Orion Poplawski
Modified: 2012-03-13 12:10 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-03-13 12:10:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2012-03-13 10:53:14 EDT
Description of problem:

The hardware clock needs to get set on hibernate.  Seems like pm-utils should handle that.

Version-Release number of selected component (if applicable):
pm-utils-1.4.1-12.fc16.i686
Comment 1 Jaroslav Škarvada 2012-03-13 11:48:04 EDT
This was disabled by upstream:

> * 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 -- 1.2.2.1 and earlier
  always synchronized clocks, but doing so is slow and most hardware stays in
  sync without assistance.

Add NEED_CLOCK_SYNC="true" to /etc/pm/config.d/clock.conf and it should work on your platform.
Comment 2 Orion Poplawski 2012-03-13 11:57:28 EDT
Hmm, I could see removing for the sleep/wake, but not hibernate/thaw.  I've added the config, sorry for not noticing that.
Comment 3 Jaroslav Škarvada 2012-03-13 12:10:34 EDT
NP, closing.

Note You need to log in before you can comment on or make changes to this bug.