Bug 159081
| Summary: | Clock runs twice as fast unless noapic is used | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kyle R Maxwell <krmaxwell> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | pfrields, tidus3012, toshio, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-06-20 13:58:08 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Kyle R Maxwell
2005-05-29 02:19:15 UTC
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 fix" ... Will there be a comment in the release notes for FC4 regarding the issue and the workaround? 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. |