Red Hat Bugzilla – Bug 234113
[RHEL5] system datetime is getting slower and slower
Last modified: 2009-03-27 10:45:48 EDT
Description of problem:
After synchronizing datetime with hw clock, the system time is getting slower
and slower. The system date is getting about twice slower. For example, now
hwclock time is: 20:00:00PM, after 5:00 min, the hw clock time is 20:05:00PM,
but the system time (date) is around 20:02:30PM. After 10 min, the hw clock time
is 20:10:00PM, but the system time (date) is around 20:05:00PM.
Version-Release number of selected component (if applicable):
I tried in both gnome (the time shown in the upper right corner), and kde, and
got the same result.
I also tried from terminal using date command.
Steps to Reproduce:
Fixing component and reassigning.
Can you attach /var/log/dmesg? Also a lspci output?
I want to see what timesource is being used, and what the chipset is.
It happens when I use xen kernel. But it is ok with regular kernel on the same
(In reply to comment #2)
> Can you attach /var/log/dmesg? Also a lspci output?
> I want to see what timesource is being used, and what the chipset is.
Can you please provide a little more data.
1.) What is the hardware you are using. Vendor, Model, Bios version
2.) Can you please run the following commands and post the output.
b.) cat /sys/devices/system/clocksource/clocksource0/available_clocksource
c.) cat /sys/devices/system/clocksource/clocksource0/current_clocksource
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Please provide info on clocksource being used, or attach /var/log/dmesg or sysreport (even better). Also provide some info on the type of system (mainboard vendor/model and processor vendor/model). There are many different causes of timeskew such as this. The requested information is essential to diagnosing and fixing this problem.
This BZ has been in a NEEDINFO state for a while now. Many timekeeping fixes have been applied to the Xen kernel since this bug was last active. Can we confirm this problem still exists and close this bug if there is no longer an issue?
Closing due to lack of response to need info request. Please reopen if you can supply the data required to work this issue.