From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv:1.7.10) Gecko/20050719 Red Hat/1.0.6-1.4.1 Firefox/1.0.6 Description of problem: The system time lags about 16s daily compared with hardware time. Compared with the greenwich time, the hw time is more accurate. http://wwp.greenwichmeantime.com/time-zone/usa/north-carolina/index.htm Version-Release number of selected component (if applicable): kernel-utils-2.4-8.37.7 How reproducible: Always Steps to Reproduce: 1. a fresh installation of RHEL 3 U5, RHEL 4 U1 or RHEL 2.1 U4. 2. hwclock --systohc 3. compare the system time with hardware time after 24 hours Actual Results: The system time lags about 16s everyday. Additional info: This problem has been reproduced on 3 IBM X445 servers. The BIOS has been updated to the latest. http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-54089 It mentioned that the lastest BIOS fixed a time syncronizing problem. http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55708&selectarea=SUPPORT&tempselected=5
Created attachment 117822 [details] time log customer record the hardware time and system time in every 10 minutes. hardare time system time 2005-08-05 16:00:01 2005-08-05 16:00:00.778561
I see no reason that this is a kernel-utils bug. Refiling against kernel.
Hello, Dawson. Why do you think this is a software problem? Do the hardware specs guarantee a clock frequency accuracy of <16 secs/day? Can you use NTP to keep the time-of-day in sync with a more accurate time source?
Hi Petrides, The hardware drifting time is less than 2s/day compared the Greenwich time. I have already suggested customer to use NTP and time base. Customer wants Red Hat to confirmation that this is a hardware problem.
My impression is that the hardware clock interrupt frequency is not typically guaranteed to be more accurate than the drift you're seeing. You should run NTP to sync with a machine having a more accurate time base. Closing as NOTABUG.