Red Hat Bugzilla – Bug 174068
Time gone mad
Last modified: 2015-01-04 17:23:13 EST
Description of problem:
After installing FC5-T1, I've noticed that system time on the machine is going
way too fast - after 25 actual minutes passed, computer is showing 20 minutes
more. Looking at seconds counter, I can tell that it's going at almost double
the normal speed.
Version-Release number of selected component (if applicable):
Not sure which component this relates to but it is happening on stock
(kernel-smp-2.6.14-1.1696_FC5) and development (kernel-smp-2.6.14-1.1707_FC5)
i686 kernels. Also, is it normal that installer selected smp kernel for
PresarioM2000 laptop, with Turion 64 CPU?
Steps to Reproduce:
1. Turn the machine on
2. Watch the clock running
3. File 'new' in bugzilla
Not sure what else can I provide at this stage - will be happy to upon suggestions.
This bug is also present in FC4 and there is already a bug entry.
OK guys, I've checked that FC4 bug entries, although I haven't had any similar
problems while running Core 4 on this same machine.
It appears that only smp kernels suffer from that particular issue, mostly on
AMD 64 processors. I've just installed and booted kernel-2.6.14-1.1696_FC5 -
seems that this one handles rtc well.
As a side note, smp kernels need mem=nopentium option passed at boot time for
successful start, single CPU kernel does not.
the mem=nopentium thing isn't needed in the current builds from rawhide.
can you paste your lspci output please ?
Created attachment 121671 [details]
PCI bus list
Here's the long listing.
Created attachment 125753 [details]
Output from lspci
This happens to me on FC5test3 on x86_64
System time is about _twice_ as fast as real time.
`sleep 60` runs in about 28 seconds.
Acer Ferrari 4005WLMi
AMD Turion64 2.0GHz
FWIW, this happens with both 'userspace' and 'performance' CPU governors.
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 36
model name : AMD Turion(tm) 64 Mobile Technology ML-37
stepping : 2
cpu MHz : 2000.000
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm
3dnowext 3dnow pni lahf_lm
bogomips : 3988.13
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
Looks like it is fixed in kernel-2.6.15-1.2032_FC5.x86_64.rpm
Vlad, fixed for you too ?
FWIW, it is also fine with kernel-2.6.15-1.2039_FC5.x86_64.rpm
Dave, I don't know if this may help:
From the excellent:
With a current kernel (2.6.14), the only major problem of this machine (not
counting buggy ACPI DSDT) is a very annoying IO-APIC bug causing system timer
to run twice as fast as it should. For now it can be rectified with a
following kernel option:
added to "image ... append=" section of the lilo.conf or "kernel" line of the
[JoÃ«l]: We got one positive report that "disable_timer_pin_1" works with
64-bit and 2.6.14-gentoo-r2. That flag allows APIC to operate, unlike
"no_timer_check". So try it :-)
Closing per previous comments.
Thre are a few other bad time/APIC related bugs floating around still open.