Bug 167698
| Summary: | system clock speeds up on load | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Noa Resare <noa> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4 | CC: | pfrields, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 2.6.12-1.1456_FC4 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-05-05 01:30:42 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
Noa Resare
2005-09-07 11:10:48 UTC
Created attachment 118548 [details]
dmesg
Preliminary tests with kernel-smp-2.6.12-1.1456_FC4 indicates that this problem has been solved. Thanks! Since my wonderful corporate network admins firewalled off the ntp port this problem resurfaced. However, some preliminary testing shows that passing the no_timer_check=0 option to the kernel at boot time works around the problem. I leave this one as closed since the problems can be worked around, but obviously it isn't really fixed so if any of the kernel wizards wants to take a look at it I'm more than willing to test patches etc. Finally I see the pattern. The system clock speeds up when the system load goes up. One testcase written in java that accesses a local oracle database seems to trigger this behaviour extremely efficiently. Test takes about 5 seconds wall clock time, but ~10 seconds system clock time due to the speedup. The problem goes away when noapic is specified at boot time. The problem also goes away when I boot the vanilla 2.6.13.4 kernel from kernel.org (with standard config). Mass update to all FC4 bugs: An update has been released (2.6.14-1.1637_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. |