Red Hat Bugzilla – Bug 335151
kernel 22.214.171.124-61.fc6 on intel xserve x345 hardware looses time badly
Last modified: 2008-02-07 23:24:50 EST
Description of problem:
ntpd on kernel 126.96.36.199-61.fc6 on an intel xserve x345 (dual hyperthreaded xeon)
can't keep in sync. Booting with clocksource=acpi_pm made kernel-188.8.131.52-57.fc6
happy and keep time, but that workaround fails on 184.108.40.206-61.
messages show [ when booted with clocksource=acpi_pm] :
Oct 15 22:14:32 db01 ntpd: synchronized to 10.0.5.254, stratum 3
Oct 15 22:14:35 db01 ntpd: time reset +2.423105 s
Oct 15 22:14:35 db01 ntpd: kernel time sync enabled 0001
Oct 15 22:17:57 db01 ntpd: synchronized to LOCAL(0), stratum 10
Oct 16 02:59:54 db01 kernel: set_rtc_mmss: can't update from 0 to 59
Oct 16 02:59:59 db01 last message repeated 5 times
And then time begins to get lost -- more than an hour over 12 hours.
When booting w/o clocksource=acpi_pm, we also loose lots of time -- on the order
of 4 seconds per minute.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Boot kernel on intel x345 server box, run ntpd, watch time get lost.
can't keep time, even with local NTPD server, whereas kernel
kernel-220.127.116.11-57.fc6 w/ boot option clocksource=acpi_pm kept us in sync with
stratum 3 NTPD on the local net.
keep time, at least within tolerance for NTPD to help us out.
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
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!
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.
Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!