Hi I have not found a solution to my problem. My servers clock (Celeron 1.4Ghz) is running very very slow. It changes the second only once every 10 seconds or so... "hwclock" is running as it should, but "date" gives totally wrong time. I have no idea where to look for... Jaska.
A new motherboard battery is where I would start. If you've looked into the bios and it is keeping time correctly then the battery is the way to go. ::I have not found a solution to my problem. ::My servers clock (Celeron 1.4Ghz) is running very very slow. ::It changes the second only once every 10 seconds or so... ::"hwclock" is running as it should, but "date" gives totally wrong time. ::I have no idea where to look for... -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
Er... I think not. The hardware clock, which runs from the battery, he says is running correctly. However, the system clock, which is updated by the CPU from an interrupt, is running 10 times slow. -- Cheers, Carlos Robinson El 02.10.06 a las 14:00, Ben Rosenberg escribió:
Date: Sun, 6 Oct 2002 14:00:22 -0700 From: Ben Rosenberg
To: suse-linux-e@suse.com Subject: Re: [SLE] system clock still running VERY sloq A new motherboard battery is where I would start. If you've looked into the bios and it is keeping time correctly then the battery is the way to go.
::I have not found a solution to my problem. ::My servers clock (Celeron 1.4Ghz) is running very very slow. ::It changes the second only once every 10 seconds or so... ::"hwclock" is running as it should, but "date" gives totally wrong time. ::I have no idea where to look for...
Hi True.. and I can't seem to find any place, where I could affect to this slow running clock. So it is still running slow.. I set the system clock to correct time yesturday evening, and now after 12 hours it is about 9 hours behind. I have tried to play around with hwclock parameters, but it does not make any difference Jaska. On Monday 07 October 2002 03:39, Carlos E. R. wrote:
Er... I think not. The hardware clock, which runs from the battery, he says is running correctly. However, the system clock, which is updated by the CPU from an interrupt, is running 10 times slow.
The 02.10.07 at 09:10, jaakko tamminen wrote: Are you running xntp or ntpdate or something similar? Those things serve to adjust the clock, and perhaps they have gone way off. If I remember correctly, just delete the file, and then echo "0.0 0 0.0" > /etc/adjtime that should reset the adjuster, if present. Perhaps you should kill the daemon first, or just delete the file and reboot. [...] I just read you solved it after an update. Then we'll never know what it was. -- Cheers, Carlos Robinson El 02.10.07 a las 09:10, jaakko tamminen escribió:
Date: Mon, 7 Oct 2002 09:10:51 +0300 From: jaakko tamminen
To: suse-linux-e@suse.com Subject: Re: [SLE] system clock still running VERY sloq Hi
True.. and I can't seem to find any place, where I could affect to this slow running clock.
So it is still running slow.. I set the system clock to correct time yesturday evening, and now after 12 hours it is about 9 hours behind.
I have tried to play around with hwclock parameters, but it does not make any difference
Jaska.
On Monday 07 October 2002 03:39, Carlos E. R. wrote:
Er... I think not. The hardware clock, which runs from the battery, he says is running correctly. However, the system clock, which is updated by the CPU from an interrupt, is running 10 times slow.
Hi I tried to play around with hwclock, that uses the /etc/adjtime file, but it did not make any difference... well, it might have made some 0.0x% adjustment, but it was not the problem. As You said, perhaps we'll never know what it was. Now it is working 100% after the update. Jaska. On Friday 11 October 2002 02:58, Carlos E. R. wrote:
The 02.10.07 at 09:10, jaakko tamminen wrote:
Are you running xntp or ntpdate or something similar? Those things serve to adjust the clock, and perhaps they have gone way off. If I remember correctly, just delete the file, and then
echo "0.0 0 0.0" > /etc/adjtime
that should reset the adjuster, if present. Perhaps you should kill the daemon first, or just delete the file and reboot.
[...]
I just read you solved it after an update. Then we'll never know what it was.
Hi I did an full online update (SuSE 8.0), and now the system clock is running fine. So, it was a SW problem, but where, I don't have an idea. Jaska. On Monday 07 October 2002 03:39, Carlos E. R. wrote:
Er... I think not. The hardware clock, which runs from the battery, he says is running correctly. However, the system clock, which is updated by the CPU from an interrupt, is running 10 times slow.
participants (3)
-
Ben Rosenberg
-
Carlos E. R.
-
jaakko tamminen