Red Hat Bugzilla – Bug 159081
Clock runs twice as fast unless noapic is used
Last modified: 2015-01-04 17:19:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
The clock runs twice as fast (e.g. gains 60 minutes in 30 minutes) unless the noapic option is passed to the kernel or APIC is disabled in the BIOS. I'm running an ECS RS480-M motherboard with an Athlon 64 3500+ processor. NTP does not 'hold back' the clock to appropriate time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start kernel without noapic and observe the clock.
2. Reboot and pass "noapic" in grub.
Applying the patch at http://lkml.org/lkml/2005/4/6/206 and passing the
parameter "timerhack" to the kernel solved the problem. This is using FC4 test
3, kernel 2.6.11-1.1366_FC4.
does this box have an nforce chipset by any chance ?
No, I think it's an MSI-based board. In any case, it's definitely not nForce
(has onboard ATI graphics).
lspci output ?
Created attachment 115158 [details]
Output of lspci -vv
Have the same problem with my Athlon64 3000+ ... Not an nForce based board. I
connot disable APIC because it causes a hangup at "Applying seagate errata
Will there be a comment in the release notes for FC4 regarding the issue and the
This sounds like Bug #152170.
The FC4 final kernel (kernel-2.6.11-1.1369) has a boot option no_timer_check
that works for me. It seems to be implementing a later version of the timerhack
patch referenced earlier in this bug.
You're right, it is a dupe. Sorry I missed it earlier.
*** This bug has been marked as a duplicate of 152170 ***