Bug 156051 - Time runs at 2x while suspended
Time runs at 2x while suspended
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-26 21:14 EDT by Eli
Modified: 2015-01-04 17:19 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-03 20:13:45 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 Eli 2005-04-26 21:14:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
When I suspend my Toshiba Satellite, time seems to run at 2x normal for the PC.  So if I suspend at 10:00, and resume at 11:00 ( 1 hour later ), the PC thinks it is 12:00 (2 hours later).
I have not specifically measured the 2x factor, but that "seems right" based on day-to-day experience.

Version-Release number of selected component (if applicable):
kernel-2.6.10-1.770_FC3

How reproducible:
Always

Steps to Reproduce:
1. Suspend notebook (close lid)
2. Resume notebook (open lid)

  

Actual Results:  3. Time has sped by for the PC.

Expected Results:  3. Time should match my watch.

Additional info:
Comment 1 Dave Jones 2005-07-15 16:07:31 EDT
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.
Comment 2 Eli 2005-08-01 19:53:30 EDT
This problem appears to be fixed for a fully updated FC3.  Thanks! :) 

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