We ran into a slightly different situation on a Compaq DL380- where the clock was running way to fast. Each second of real time saw the system clock gain 2-3 seconds. We were convinced this was a software problem, and NTP refused to set the clock after it drifted too far off. Booting into RescueCD and Windows revealed that the problem still existed. I finally ran hardware diagnostics on the unit, and it turned out that the CMOS chip (IIRC) consistently failed. The final fix was to replace the motherboard with a known good unit, and the problem went away. I was so sure it was a software issue that I ignored hardware possibilities for many days. -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Sean Carlos Sent: Wednesday, November 16, 2005 4:22 PM To: For users of Fedora Core releases Subject: Re: Clock issues akonstam@xxxxxxxxxxx wrote: > On Thu, Nov 10, 2005 at 06:49:01AM -0500, Bob Chiodini wrote: > >>On Wed, 2005-11-09 at 10:40 -0800, Brian D. McGrew wrote: >> >>>Running a Dell PE850 with FC4 installed. I used rdate -s to set the >>>clock and the time is correct. I even have it in the crontab tab. >>> >>>When the machine reboots, the clock is wrong, way wrong by anywhere from >>>6 to 12 hours. How do I get the clock to sync up at reboot time? >>> >>>-brian >>> >>>Brian D. McGrew { brian@xxxxxxxxxxxxx || brian@xxxxxxxxxxxxxxxxxxx } >>>-- >>> >>>>Those of you who think you know it all, >>> >>> really annoy those of us who do! >>> >> >>Brian, >> >>Are you cleanly rebooting the system? >> >>/etc/init.d/halt contains code to set the hardware clock to the system >>(software) clock. Unless the motherboard battery is failing, or the >>system was not properly shutdown/rebooted the H/W clock should not drift >>that much. >> >>Running rdate from cron only sets the system clock, not the H/W clock. >>You should also run hwclock --systohc in the same cron job. >> >>As suggested by Yonas and Alexander, NTP is another solution, but it >>will not correct the H/W clock by itself. You still must insure that >>hwclock runs, either periodically, or at shutdown. >> >>What is the BIOS time immediately after shutting down? >> >> >>Bob... > > This is a periodic problem that someone down here was complaining about > just today. When you boo t hwclock is run to set the system clock to > the hardware clock. That code is in /etc/rc.d/rcsysinit > > When you halt hwclock is run to reverse the process. That code is in > /etc/init.d/halt. > > Check to see that the running of the hwclock -systohc and > hwclock -hctosys both run correctly. Further check whether the hwclock is > drifting due to a weak battery. I also had this problem on two different Dell desktops. For one (Dimension 4700), the solution was discussed here: https://www.redhat.com/archives/fedora-list/2005-April/msg04936.html If [root@localhost ~]# hwclock --systohc select() to /dev/rtc to wait for clock tick timed out does not work but [root@localhost ~]# hwclock --systohc --directisa works, then add a CLOCKFLAGS=--directisa line to the /etc/sysconfig/clock file. Look at /etc/rc.d/init.d/halt at around line 115 to see how that works. For a Dimension 8400? the solution was to add dev.rtc.max-user-freq = 1024 to /etc/sysctl.conf Sean -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list The information contained in this e-mail including any attachments may constitute Corvis Equipment Corporation Proprietary Information that is subject to Non-Disclosure Agreement and cannot be disclosed to any other party without the express consent of Corvis Corporation. If you are neither the intended recipient of this e-mail nor responsible for delivering this e-mail to the intended recipient, note that any dissemination, distribution, copying, or retention of this e-mail is prohibited. If you believe you have received this e-mail in error, we request that you notify the sender by return e-mail and then delete this e-mail and any return email immediately.
