Bug 270321
Summary: | tsc looses time and ntpd doesn't sync | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | charles harris <charlesr.harris> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7 | CC: | chris.brown |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-12-12 16:25:21 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: |
Description
charles harris
2007-08-31 06:09:20 UTC
Um, there is no 2.6.23-rc4 kernel for Fedora 7. Did you mean to file against rawhide? No, I compiled my own kernel to check out the new scheduler. I don't know that it is really a kernel specific problem as I don't know how the default clocksource is chosen. The config is the f7 one except for the new parts. I don't see anything in the config to select the default clocksource, but maybe I am missing something? (In reply to comment #2) > No, I compiled my own kernel to check out the new scheduler. It's already in the new Fedora 2.6.22 kernels. > I don't know that > it is really a kernel specific problem as I don't know how the default > clocksource is chosen. The config is the f7 one except for the new parts. I > don't see anything in the config to select the default clocksource, but > maybe I am missing something? Do the Fedora 2.6.22 kernels have the same problem? Can you try Fedora8 test2 when it's released? Latest is here, it has CFS v20.5 plus a bugfix from the mailing list: http://koji.fedoraproject.org/koji/buildinfo?buildID=17344 I gave the latest kernel a shot. As you can see from the ntpq output the tsc drift is still bad. remote refid st t when poll reach delay offset jitter ============================================================================== clock2.redhat.c .CDMA. 1 u 62 64 7 70.868 3635.60 2690.36 x1.tonyurban.co 128.105.37.11 3 u 59 64 7 52.314 3723.83 2754.86 all.ericspeaks. 8.15.10.42 3 u 62 64 7 86.755 3644.36 2667.77 This is after the first poll. On another note, I also see the boot message usb 4-1: device descriptor read/all, error -71 But it may well just be hardware or the bios. I've noticed it with both fc6 and f7 ever since I upgraded my machine. Anything else I can do? 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 and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Hi Christopher, Good news and bad news. Both 2.6.23-rc8 and 2.6.22.9-91.fc7 synced up on first boot, but 2.6.23-rc8 failed on second boot. The tsc is still chosen as the time source and still looks to be unreliable, the pm timer remains a better choice for my machine. The hpet bug is fixed in rc8, so I will give that a try also. This problem may be related to this posting on LKML: http://marc.info/?l=linux-kernel&m=119254738106753&w=2 Hello Charles, Sorry to ping you for an update and then disappear for two months. Thanks for the info anyway. Ingo indicated it has been applied so I'm closing as NEXTRELEASE 2.6.24-rc1. Please re-open if its still an issue. |