Red Hat Bugzilla – Bug 183201
TICK value set by adjtimex has no effect on ppc G4 (mac-mini)
Last modified: 2015-01-04 17:25:40 EST
Description of problem:
System time has more or less constant drift on a Mac-Mini (ppc, G4). However,
trying to compensate for this by issuing: 'adjtimex --tick 10028' (as sugested
here: http://ntp.isc.org/bin/view/Support/KnownHardwareIssues) has no effect
whatsoever. The TICK value reported by 'adjtimex -p' *is* changed to the new
value. So, I suspect a kernel bug, and not a bug in adjtimex. It's a relatively
big problem for me, because ntpd can not stabilize with such a big drift
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. invoke 'adjtimex --tick 10028'
2. observe that nothing happens, systematic drift reported by ntpd remains the same
tick value set by adjtimex does not change the systematic drift in the system time.
tick value should influence system time drift
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
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 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.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.