Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 7750 - does not keep proper time on laptop
does not keep proper time on laptop
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-12-11 03:22 EST by SI Reasoning
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-24 21:56:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description SI Reasoning 1999-12-11 03:22:44 EST
After upgrading to Redhat 6.1 from 6.0, I started noticing that the time
kept slipping. When it reboots, the time is correct but it starts losing
seconds immediately.... to the point where it can lose an hour or so a day.
I have all of the updates, including gnome, and I am running the newest
enlightenment. I also use vmware with Linux as host. I am not exactly
certain when this problem occurred but I suspect that 1 of the 3 (upgrade,
vmware, new enlightenment) may be the culprit.

I also guessed at the file "time" as the one causing the problem.
Comment 1 Jeff Johnson 2000-08-16 13:18:25 EDT
Losing time is most likely a kernel problem, changing component
Comment 2 SI Reasoning 2000-09-01 13:01:24 EDT
I have since changed laptops (upgraded to an updated model) and still have the
same problem. I went from a Chembook 7400 to a 7400-B (Asus F-7400 to F-7400B).
Comment 3 Doug Ledford 2000-09-01 22:07:08 EDT
This could be caused by the laptop loosing time while it is suspended.  Does the
time loss happen all at once or can you actually watch it happen while the
system is in use?
Comment 4 SI Reasoning 2000-09-01 23:02:31 EDT
You can watch it happen.... It loses time every minute...but nothing consistant
that can be adjusted... at least the last time I tried months ago. I currently
update my time through ntpdate cron every hour. I used to do it every minute
since the loss was so bad.
Comment 5 SI Reasoning 2000-09-02 04:39:44 EDT
Here are 8 hours worth of ntpdate updates:

1 Sep 20:01:47 ntpdate[5927]: step time server offset 106.667959
1 Sep 21:01:48 ntpdate[6198]: step time server offset 106.906458
1 Sep 22:01:48 ntpdate[6505]: step time server offset 107.019308
1 Sep 23:01:48 ntpdate[6855]: step time server offset 106.444481
2 Sep 00:01:47 ntpdate[7137]: step time server offset 105.636691
2 Sep 01:01:46 ntpdate[7421]: step time server offset 105.362106
2 Sep 02:01:55 ntpdate[7738]: step time server offset 113.298043
2 Sep 03:01:47 ntpdate[8009]: step time server offset 105.456529
Comment 6 Stephen John Smoogen 2003-01-24 21:56:52 EST
From what I remember, most of these issues listed above were related to VMWARE
module and time in the 2.2. kernel.  It was something dealing with APM, VMWARE,
and other 2.2 issues. The problem might be fixed in later VMWARE issues, but it
is not a Red Hat problem but a closed source module problem.

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