Red Hat Bugzilla – Bug 145128
hwclock timed out on recent kernels and sync problems
Last modified: 2015-01-04 17:15:37 EST
Description of problem:
In kernel2.6.10-1.741 and 2.6.10-1.737 the hw clock cannot be
read and it is also no longer possible sync the hw clock.
There were no problems in previous kernels, e.g.
2.6.9-1.724 and 2.6.9-1.681
Version-Release number of selected component (if applicable):
kernel2.6.10-1.741 and 2.6.10-1.737
type in hwclock --show
result is timed out message; kernel 2.6.9-1.724 gives the right
Steps to Reproduce:
1. hwclock --show
select() /dev/rst timed out
Fri 14 Jan 2005 05:35:11 PM CET -0.015968 seconds
Worked without problems until I updated to the latest two kernels.
It still worked if I use an earlier kernel, as mentioned above.
Somehow this got filed against syslinux. Reassigning to kernel.
I have posted a 'workaround', used on a Dell Dimension P4 w/ HT
supported and enabled running kernel/-smp 2.6.10-1.741_FC3, in bug
This bug occurs on fedora core 2 (kernel 2.6.10-1.9_FC2smp). on all my
dell 2850s. The default kernel 2.6.5-1.358smp (before doing updates)
works. I was able to work around this problem by implementing the
Dup of bug 144894?
This also occurs on a Dell Dimension 8400, under the released version of Fedora
Core 3, with the 2.6.11-1.14_FC3smp kernel.
Another mention on the debian kernel list:
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
This indeed looks like a dupe of bug #144894.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (126.96.36.199). 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.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is fixed in 2.6.14-1.1637_FC4