Bug 476051 - PC clock has 20 minutes drift
Summary: PC clock has 20 minutes drift
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-11 18:12 UTC by Alexander Todorov
Modified: 2009-12-18 07:15 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-18 07:15:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2008-12-11 18:12:43 UTC
Description of problem:
The time value differs substantially with correct local time after about 8hrs.

Version-Release number of selected component (if applicable):
kernel-2.6.27.7-134.fc10.i686

How reproducible:
Always

Steps to Reproduce:
1. boot into BIOS and set the correct time. (UTC value)
2. boot Fedora (ntp is disabled). Set appropriate timezone.
3. After 8hrs of beeing up (and almost idle) the value in GNOME's clock applet differes substantially from the correct time.
  
Actual results:
Time differes

Expected results:
Time stays the same

Additional info:
ntp is disable
cpu frequency scaling is disabled and not supported by CPU
mother board battery is OK (tested by leaving the PC into BIOS settings screen after reboot for more than 12 hrs. no change).

$ date && hwclock --show
Thu Dec 11 19:54:31 EET 2008
Thu 11 Dec 2008 08:10:44 PM EET  -0.533023 seconds

hwclock shows correct time but date not.

Comment 1 Michal Jaegermann 2009-02-03 16:46:57 UTC
Did you look at bug 476609? I am not sure if this the same issue as effects were much more severe.  Before I supplied 'clocksource=jiffies' the affected machine was unusable.

Comment 2 Alexander Todorov 2009-02-04 11:05:26 UTC
I'm not seeing the severe problems you do. I only have my clock out of sync from the actual time. Nit sure if this is a dupe. Will test with 'clocksource=jiffies' and see if the situation improves.

Comment 3 Alexander Todorov 2009-02-04 17:04:50 UTC
clocksource=jiffies works for me

Comment 4 Bug Zapper 2009-11-18 09:40:07 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-12-18 07:15:59 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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