CPU clock running WAAAAY too fast...

[Doomhammer]

I'm having a problem where basically the system time progresses more than twice as fast as normal ... i.e. I gain about 2 seconds after every 1 second passes.

I've seen various threads on the internet discussing this, but none of the fixes they offered have worked so far (I've tried both no_timer_check and no_acpi)... It seems to be somehow caused by the ATI XPRESS 200 chipset.

This system is running an AMD Sempron, not overclocked, and an ATI XPRESS 200 chipset motherboard.

[psycepa]

have you tried to set the SYS_TO_HC var in AFAIK /etc/conf.d/clock or sth to yes ?
_________________
RLUNo. 376073
bo czytac, to trzeba ze zrozumieniem (c) by psycepa
"nigdy nie kloc sie z glupcem, najpierw sprowadzi cie do swojego poziomu a potem pokona doswiadczeniem"
"Life is complex. It has its real and imaginary part."

[Doomhammer]

[Doomhammer]

Fixed, passing the noapic option to the kernel at boot fixed it.

[1clue]

Hi,

I've noticed this problem since RedHat Enterprise Linux 3.0, on multiprocessor kernels.

I'm currently using Gentoo 2.6 with the same box, and this problem drives me nuts.

Does the noapic kernel parameter cause SMP to not work right? I'm in the middle of looking, I notice it applies to apic and SMP options. The kernel documentation has an MSI-HOWTO.txt file that goes into APICs but I don't completely understand it by context.

I'm using a P4, which has that funky 1.5 CPU situation, there's only one CPU and it looks like there are two. There's a noticeable improvement by using an SMP kernel, so I don't want to disable SMP.

Thanks.

[mudrii]

Try to set in you kernel RTC and HPET Timers, I had the same problem with Nforce4 Chip set before.
_________________
www.gentoo.ro

[1clue]

[mudrii]

I have my kernel compile with

[1clue]

Thanks, I'll give it a try.

[1clue]

[kheisler]

I'm having the same issue (but with my installed system, not just the livecd).
I've tried both the HPET and RTC kernel option and the noacpi flag, but i'm still in a time warp.

anymore suggestions?

[feld]

http://video.google.com/videoplay?docid=1165426646799887272&q=insane+time


This is a good example of what can happen when you have this issue.
_________________
< bmg505> I think the first line in reiserfsck is

if (random(65535)< 65500) { hose(partition); for (i=0;i<100000000;i++) print_crap(); }

[kwispy]

I've had the same problem ever since I reinstalled Gentoo on my desktop. My system time is not twice as fast as normal, it just accumulates a few extra seconds every minute, so that the end result after a week's time is about 30-40 mins ahead of normal time. The funny thing is is that my hw clock shows the correct time, while my system clock, which I've heard is what the kernel controls runs fast.

Check this out:

[kg4ysy]

I get the write times in the future stuff all the time. To make sure my clock is right, I just run ntpd at startup so it sets the clock correctly and then syncs it to the hwclock. The hwclock seems to be behind when I restart since it says the write times are in the future. I've just learned to deal with it by using ntpd.

--Jim

[koenderoo]

Possible answer in this thread: https://forums.gentoo.org/viewtopic-p-3833197.html#3833197

Short: change the multiplier in /etc/adjtime (first number in that file) to either 10000.000000 or a multiplier that suits you.
_________________
webmaster van www.koenderoo.nl