System clock runs too fast depending on CPU charge

Bug #155882 reported by Kevin Gagnon
This bug report is a duplicate of:  Bug #17589: System clock runs far too fast. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

Here is my system configuration :

Asus motherboard P5W
Intel Core2Duo
2gig Ram
NVIDIA 8800GTS

Running Gutsy (7.10)

As you can see, this is fairly new and recent hardware.

The problem is when I ask some performance task to my system ( compiling, playing WoW or listening to music) the clock suddently go faster. It can take up to 20min in a few hours of gaming.

I checked the BIOS time to see that it is keeping it's time. When I reboot into Ubuntu, the clock is alright and back to the good time.

I tried to sync the clock via NTP but sometimes it just fails because there is too much difference between my clock and the time server.

Any ideas?

Revision history for this message
Kevin Gagnon (gagnon-kevin) wrote :

I did some research and someone suggested that I should change de CMOS Battery. This is a not a problem because the BIOS time is always accurate.

Someone also suggested to install 64-bits kernel. Just to be sure, I did a clean install and the problem is still present. The clock is running to fast.

Revision history for this message
Samuel Fogh (gaffa) wrote :

I confirm this bug. My clock is acting very strange.

Revision history for this message
Samuel Fogh (gaffa) wrote :

I just booted to try and debug the issue, but my clock appears to act normal.

Revision history for this message
Kevin Gagnon (gagnon-kevin) wrote :

I tried booting with "no_timer_check" and it seems to have fix the clock.

This can be a workaround but for some non-tech people this bug can be really annoying.

Revision history for this message
Kevin Gagnon (gagnon-kevin) wrote :

The above solution works for 64 bits kernel.

For ubuntu 32bits, i had to add "clock=pmtmr" on boot to get it under control.

Ubuntu 32bits -> Boot with "clock=pmtmr"

Ubuntu 64bits -> Boot with "no_timer_check"

Again, this is a workaround because it does not fix the "real" problem. Can be a killer issue for average joe user...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.