Bug 211902
| Summary: | Time runnig at double speed on 2.6.18-1.2200.fc5/2.6.18-1.2798.fc6 (i586) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Bentley <david.r.bentley> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 6 | CC: | johnstul, jonstanley, samuel-rhbugs, vnk, wtogami | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i386 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | F8 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2007-12-31 07:05:31 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
David Bentley
2006-10-23 19:22:00 UTC
Created attachment 139158 [details]
dmesg output
Created attachment 139159 [details]
dmesg output
Created attachment 139649 [details]
dmesg output
I originally filed this bug against the latest kernel for FC5 but just having
installed FC6 the default kernel has the same problem on my ASUS P5A so I will
be reverting it back to FC5 after this bug update.
Modifying bug to FC6 but it may be more appropriate to leave it as FC5 or even show it as DEVEL as this is where the frantic kernel updates will get done once FC7 development starts in ernist. IF it would help I could run this system in rawhide mode or just boot into any test kernel for FC5 to help diagnose the problem. Updated to show FC6 Kernel in summary does it go normal again if you boot with clocksource=tsc ? Looks to be due to the removal of verify_pmtmr_rate(). If I recall, it was pulled as it slowed down boot times and there was some question as if it was actually necessary (x86_64 didn't need it). The question now regarding a fix is: 1) Do we just blacklist the affected chipset, using the current acpi_pm blacklist infrastructure? Or... 2) Re-add the verify_pmtmr_rate dynamic detection code. Thoughts? I can confirm that if you boot with clocksource=tsc all is now well using the latest FC5 kernel (2.6.18-1.2239.fc5) on my ASUS P5A box. I presume the same fix should work for FC6 but I will wait for confirmation before going through a backup of all data and installing FC6. Presumably I could add this parameter during instalation so I may be able to test if the fix works for FC6 without having to re-install if there is some way of checking the time (from a console perhaps) before you commit yourself to do the install. David, could you please attach dmidecode output? A fix for this (re-adding the verify_pmtmr_rate code) has been sent to Andrew. I have tried the above recommendations and this didn't correct the time on my computer. Please advise how I should proceed. I have added clocksource=tsc to the /etc/grub.conf file and the clock is now running at normal speed. I have 2.6.19-1.2895.fc6 for my kernel clocksource=tsc worked for me too. I was really wondering what was going on when my server started running at double time... Re comment #9 Sorry I missed the request for further info my ISP's spam filter has occasionally been eating e-mails that should get forwarded to my test-list folder. Anyway I am attaching it now. Created attachment 147696 [details]
Info as requested sorry for the delay hope it helps
System is now running FC6 and since instalation has had the suggested fix (i.e
clocksource=tsc) added to the grub file.
System is currentl upto date running the latest kernel and I havent tried it
without the fix.
Per comment #15, I'm not sure whether you think that this bug can be closed or not. Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora! I'm running F8 now and I don't need that kernel parameter. It's working fine now. In that case, I'll close this one CURRENTRELEASE. Thanks! |