Bug 239714 - After resume from RAM, my hardware clock is off by decades :(
After resume from RAM, my hardware clock is off by decades :(
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-10 14:23 EDT by Zack Cerza
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-20 11:53:18 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 Zack Cerza 2007-05-10 14:23:32 EDT
Description of problem:
Every time I resume from RAM, my hardware clock is over 1 decade ahead or behind
 real time. Year, month, day and time are all affected. Sometimes I'm in the
1970s, and sometimes I'm in the 2020s. The "software" clock seems to keep the
right time.

I'm reasonably confident FC6 didn't do this on this hardware (Thinkpad X41).

I realize there's probably not enough information here, but I'm not sure what to
provide; I don't see any interesting messages in any logs or dmesg when this
occurs. Let me know what I can do.

Version-Release number of selected component (if applicable):
kernel-2.6.21-1.3132.fc7.i686
kernel-2.6.21-1.3141.fc7.i686
and some previous ones

How reproducible:
Always
Comment 1 Nigel Cunningham 2007-05-18 18:46:24 EDT
Sounds like CONFIG_PM_TRACE is enabled. Are you able to check whether that's true?
Comment 2 Chuck Ebbert 2007-05-18 19:07:01 EDT
(In reply to comment #1)
> Sounds like CONFIG_PM_TRACE is enabled. Are you able to check whether that's true?

http://cvs.fedora.redhat.com/viewcvs/rpms/kernel/F-7/configs/config-generic?root=extras&rev=1.315&view=auto

Says it is.
Comment 3 Zack Cerza 2007-06-20 11:53:18 EDT
Haven't seen this in a while.

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