Weird PC Clock Behavior? 70
cybercyst asks: "I've been having a problem with this for quite some time, and thought it was just me -- until two good friends of mine experienced the same problem. What we are experiencing is best described as a time-skew: our system time is apparently jumping forward an hour, and then returning to normal. It repeats this multiple times, and as far as I can tell only a reboot is any sort of remedy for this, albeit a temporary one. As you can imagine this causes all sorts of problems (under windows managers xscreensaver is always popping up -- in fact as I wrote this, the screensaver has come on over 10 times, negative fps in OpenGL programs, extremely large ping times, and so forth)."
"Friend A runs an Athlon system on a Soyo Dragon motherboard, I'm running a K6-2 450Mhz CPU on an older Epox motherboard. We are both running Slackware 8.0 with kernel 2.4.17, but Friend B runs nothing but Red Hat, and kernel 2.4.2-2.
I have personally tried many things to get this fixed permanently, including setting the time with 'date -s; hwclock --hctosys; hwclock --systohc' the BIOS is set to the right time that doesn't seems to help! So, I'm asking Slashdot, Has anyone out there encountered a similar problem, and if they have, have you been able to fix it?"
Time/space anomaly (Score:5, Funny)
Try a tatacion burst, that normaly helps...
Try Truetime (Score:4, Informative)
Re:Try Truetime (Score:2, Funny)
Re:Try Truetime (Score:1, Funny)
Re:Try Truetime (Score:1)
Win2K (and I assume WinXP) dont have these time loss and slowdown features.
Re:Try Truetime (Score:3, Interesting)
Re:Try Truetime (Score:1)
Re:Try Truetime (Score:3, Insightful)
Re:Try Truetime (Score:1)
Re:Try Truetime (Score:2)
Re:Try Truetime (Score:2)
As true time was primarily a government contractor, At least a few people in the army thought that was a completely acceptable bug fix.
Daylight saving changes (Score:1)
Re:Daylight saving changes (Score:1)
Not possible if you use any other OS on the same machine, though.
Has anyone seen a UTC hwc TZ .reg for Windows? (Score:1)
Of course, I did not bookmark it, and can not find it again now.
---
Emacs (GNU?) changing names from Win32 to W32, cause Win implies a positive user experience.
The solution might be this... (Score:5, Informative)
'man 8 hwclock' and 'The Adjust Function' might give you some answers.
Give it a shot, at least.
Are you sure (Score:4, Funny)
Have you by chance opened an e-mail with subject "Good Times"? You should have deleted it upon receipt. Now you're infected. And, because of the name "Good Times", it sure can change your computer time.
That was an easy one. Next !
Re:Are you sure (Score:1)
Re:Are you sure (Score:1)
Do you believe in virus e-mail warnings?
Well, that good times warning didn't say anything about OS. So it sure is multi-plataform.
Re:Are you sure (Score:1)
Re:Are you sure (Score:2, Informative)
Re:Are you sure (Score:1)
Symantec [symantec.com] has a write-up on it, and has had for a long time now.
My opinion (serious) (Score:5, Interesting)
Computers have a clock to keep time. Usually there is a hardware clock with battery backup to keep time when the computer is off. The operating system (for example Linux) runs its own clock, and from this clock comes the time shown by commands such as date in Linux and time in DOS.
The hardware clock is usually accurate enough, provided that the battery has not run out. If the time shown by the computer when you turn it on is wrong by several months or years, it is worth checking if the battery is still usable.
The "software" clock in the operating system usually has drift, either systematic or random. This drift means the clock runs too fast or too slow. For this reason it is necessary to use some accurate time source to syncronize the operating system clock if accurate time is needed.
[my opinion:] Normally I'd just say: Use NTP [udel.edu]. But your random time drift seems to be so high, NTP would freak out.
It seems to be a hardware problem, or some friend made a practical joke on you, inserting some random time drift in crontab. Try to reinstall your OS and check if this behavior continues. If so, you should change your motherboard. And try to get a good one, like Asus.
Time Shifts Can Be A Matter Of Life Or Death (Score:4, Informative)
We have never figured out how to stop the computer time from jumping and if anyone else has, please let me know! The workaround solution we've come up with is to either install a network time update program running in the background if the computer is on the web (for examples, search for "time sync" here [zdnet.com]or for the more common rural EMAs that have no Internet connection, we install clock boards. We have found three sources for clock boards: Beagle Software [beaglesoft.com], OutSource [outsrc-em.com] and ICS Advent [icsadvent.com]. The Beagle product is ISA only, the OutSource product only works with Win 2000/NT (not Win 95/98) and the ICS product is far and away the most expensive. If anybody knows of others besides these three, please let me know!
GPS (Score:2)
It's not the microsecond accuracy that specially-designed GPS systems have, but it'll definately be accurate to within a few seconds.
Even a simple $99 Garmin eTrex could probably solve your problems, although you might want to go with a more expensive unit with an external antenna (maybe the eMap). Or you could buy one of the dedicated serial GPS modules, like the Garmin 35.
Re:GPS (Score:2)
Now, if Garmin came out with a cheap GPS that plugged directly into ethernet instead of a serial port, then we'd have something....
Re:GPS (Score:2, Informative)
Hokey name, but I'm told it works pretty good. The local telco (MTS) uses one for it's time source.
Cheers!
John
CDMA effectively rebroadcasts GPS time (Score:2)
use ntpd (Score:4, Insightful)
for more info on how linux keeps time checkout the hwclock and adjtimex man pages.
Re:use ntpd (Score:2)
That's a pretty good assumption. Though, your powers of preception could have been put to rest on this one since he specficially said all three systems having this problem were running various flavors of Linux distros and kernels.
Check your zoneinfo for possible corruption (Score:1, Interesting)
(Zoneinfo can specify pretty much arbitrary time corrections - I used to have my own timezone with daylight savings just for an hour every day, so I could fool the timeclock software about what time I got back from lunch. Amazing what unix programs will believe, even when you're not root...)
The compiled zoneinfo files are binary, so a few corrupt bits could easily do this.
Try running 'TZ=GMT date' on a regular basis, and see if the underlying system time is jumping about, or only your 'local' time....
(As another poster said, the hwclock is only used at bootup time, to set the inital clock)
Competing Time syncs (Score:4, Informative)
ntp is the most robust free time synchronization software. Try using that in preference to rdate, timed, timeslave, etc. Test ntpd by using "ntpdate" against your upstream ntpd time servers to make sure they do what you expect.
Every time I've mentioned this (Score:2)
Re:Every time I've mentioned this (Score:2)
New Battery (Score:2, Redundant)
Cheers,
levine
Re:New Battery (Score:3)
Linux Timing Problem (Score:2, Interesting)
A month ago, I wiped the system and re-installed Linux. The problem went away but, now I have a different time problem. Now, my Linux clock runs slooowww when the systems is under any sort of a load. If the systems is left idle the clock keeps perfect time. Run Konqueror for a while and the clock goes to shit. Run an editor, doesn't seem to matter which, and the clock is worthless. Hell, let a screen saver run overnight and the clock loses 5 hours.
There is a problem with the clock!
Are you sure? (Score:1)
UTC=false? (Score:3, Informative)
UTC=false
Because Windows diddles with the hardware clock directly, it can't be used (directly) as a UTC time source for UNIX.
Naturally, if you're ONLY running Linux, you can have UTC=true and forget about it.
--
Re:UTC=false? (Score:2)
I don't see where he said that.
Because Windows diddles with the hardware clock directly, it can't be used (directly) as a UTC time source for UNIX.
It can if you tell Winblows that your local time zone is UTC, and then correct it in your head when you look at the clock. Or is that just too damn geeky?
Re:UTC=false? (Score:2)
although, what you could do is have windows update time on boot (xp has built-in support for periodic time updating, other versions can do it too, but not quite as easily), and have linux update time on boot, and not care what time it is when you start running
i know the cable modem i have at home has no sense of time when it starts, it picks up the time from the cable signal (would be a nice feature of the service to allow my pc's to pick up that signal too, but *sigh*)
I suggest trying Windows :-) (Score:4, Funny)
As the original question states, this offset in time is automatically corrected upon reboot. This is due to the OS once again keying off from the far more reliable internal hardware clock.
To me, the cause/solution to this individual's issue is quite apparent. The issue is caused by running far too stable of an operating system - LINUX. As such, the somewhat obvious solution to change the installed OS to something a bit, shall we say, less reliable.
Like many, when I think of unreliability I immediately think of Windows!!! May I suggest the ME version - in my very limited experience with this product, I have found it to be most unstable...your consequently, workstation will never go without a reboot for a long enough period to ever experience time drift again!!!
Different distro, same problem (Score:1)
Until today, I thought it was just me.
Re:Different distro, same problem (Score:2)
Re:Different distro, same problem (Score:1)
shrug
An idea (Score:1)
(I don't know how offhand - anyone?)
slightly offtopic: XP losing substantial time (Score:1)
Any help would be appreciated. This is particularly annoying because I use time-sensitive applications.
Re:slightly offtopic: XP losing substantial time (Score:2)
(my laptop loses a lot of time, so i have xp synch the clock every 2 hours)
Similar Problem With Windows (Score:1)
Windows 98 loses time. (Score:1)
Search for a program called AboutTime and use that to keep your clock somewhat accurate.
Re:Similar Problem With Windows (Score:1)
HP are nortorios for this (Score:1)
Power management? (Score:4, Informative)
If you try this, you'll probably want to turn power management off both in software (remove apmd etc.) and in the motherboard's bios settings. Most motherboards should allow you to do this.
Good luck!
Timewarp (Score:1)
We submitted a problem report to the BSD guys and after a little bit, they confirmed that it was an APM problem. We recompiled the kernels without APM support and it disappeared.
External EMF? (Score:3, Informative)
Finally, I saw it happen. It was right about lunch time and on the other side of the wall was the worlds oldest radar range (pre Microwave Oven). That sucka kicked in when someone heated their lunch and the clock on the computer actually ran backwards!
I had to move the desk away from the wall several feet and the problem stopped happening.
More than likely though, the problem is with a buggy BIOS or dying battery. Replace the battery, flash your BIOS to the latest revision. If this doesn't work then you're only out about $10.00. Next step is to either buy an add-on time device that works properly or if you have a net connection running all the time, look into the NTP (Network Time Protocols) to sync with the Naval Observatory or another good source for correct time on as frequently a basis as you require.
Also check out the Linux clock features like the realtime daemon, it's not for realtime as in realtime OS but for more accurate time keeping. Red Hat has this daemon by default.
Check your security, make sure a co-worker is not just trying to mess with your head by changing your clock remotely.
It's quite simple (Score:1)
-CH