https://bugzilla.novell.com/show_bug.cgi?id=403557
User AmigaPhil@ping.be added comment
https://bugzilla.novell.com/show_bug.cgi?id=403557#c5
--- Comment #5 from Philippe Duchenne 2008-08-08 10:24:55 MDT ---
Update to comment #2 and comment #4 :
Again, my computer clock was about 1 hour 15 (?) late when I switched it on
today. I fixed the clock again, and restarted the computer. The system clock
was then still correct.
So it appears that indeed the corruption of the clock happen after a cold boot
only...
If it can help to help:
- /etc/sysconfig/clock has SYSTOHC="yes"
- /etc/init.d/boot.clock is doing (I guess) at boot :
echo -n Setting up the hardware clock
#
# Read out to hardware clock and for UTC calculate adjtime
# write back the system time later at reboot/shutdown time.
#
if test "$SYSTOHC" = yes -a "$USE_ADJFILE" = yes ; then
# For UTC calculate adjtime
#
if test ! -s /etc/adjtime ; then
echo "0.0 0 0.0" > /etc/adjtime
echo "0" >> /etc/adjtime
echo "UTC" >> /etc/adjtime
fi
/sbin/hwclock --adjust $HWCLOCK
rc_status
fi
/sbin/hwclock --hctosys $HWCLOCK
rc_status -v -r
- /etc/adjtime has this :
-10808.673458 1218205656 0.000000
1218205599
UTC
- the "11 minute mode" is off ('adjtimex --print' shows the line 'status: 64').
I assume that adjtime is maybe what is modifying my hardware clock. According
to hwclock's man pages, the first value indicate that my computer has a
systematic drift rate of 10808 seconds per day (that is 3 hours !?!) but that
does not match with the "1 hour 15 late" my system clock was at boot.
---
To Khairul Kamal Idris, Cyril Brosch :
Have you checked the man pages of hwclock ? I saw a section about the RTC
device that may help.
--rtc=filename
overrides the default /dev file name, which is /dev/rtc on many
platforms but may be /dev/rtc0, /dev/rtc1, and so on.
[...]
hwclock Uses many different ways to get and set Hardware Clock values.
The most normal way is to do I/O to the device special file /dev/rtc,
which is presumed to be driven by the rtc device driver. However, this
method is not always available. For one thing, the rtc driver is a
relatively recent addition to Linux. Older systems don't have it.
Also, though there are versions of the rtc driver that work on DEC
Alphas, there appear to be plenty of Alphas on which the rtc driver
does not work (a common symptom is hwclock hanging). Moreover, recent
Linux systems have more generic support for RTCs, even systems that
have more than one, so you might need to override the default by speci-
fying /dev/rtc0 or /dev/rtc1 instead.
[...]
hwclock tries to use /dev/rtc. If it is compiled for a kernel that
doesn't have that function or it is unable to open /dev/rtc (or the
alternative special file you've defined on the command line) hwclock
will fall back to another method, if available. On an ISA or Alpha
machine, you can force hwclock to use the direct manipulation of the
CMOS registers without even trying /dev/rtc by specifying the --direc-
tisa option.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.