[Bug 416360] New: Wrong system clock after boot
https://bugzilla.novell.com/show_bug.cgi?id=416360 User AmigaPhil@ping.be added comment https://bugzilla.novell.com/show_bug.cgi?id=416360#c403557 Summary: Wrong system clock after boot Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Booting AssignedTo: jsrain@novell.com ReportedBy: AmigaPhil@ping.be QAContact: jsrain@novell.com Found By: --- (Discussed in bug #403557) When I installed OpenSUSE 11.0, I had to set the clock. From Yast, I left the "Hardware clock set to UTC" unchecked (so the computer was supposed to have the clock set to local time). After a boot/restart, the system clock was 2 hours ahead. As my timezone is UTC+1 and we are in DST, I suspected that when shutting down, the system saved the clock as local, but loaded it as UTC (and adjusted to local). I set the clock again using Yast, this time checking the "Hardware clock set to UTC", but I still have a wrong system time after a boot/restart: the clock was 1 hour 15 minutes late. After several attempt to set the clock, with always a 1 hour 15 minute fall back of the system clock when I switch on my computer the following day, I discovered that /etc/adjtime has a "-10808.673458" seconds (3 hours ?!?) as systematic drift rate. So I fixed the clock once more; then, as root, I edited the /etc/adjtime file to reset all values to 0. Finally, I saved the system clock to the hardware clock (hwclock --systohc) so that the /etc/adjtime is restored with the right values, but without that ugly "-10808.673458" systematic drift rate (which is now equal to 0). The next day, when I switched on my computer, the system clock was correct. But today, my system clock is 30 minutes late ! (the systematic drift rate value in /etc/adjtime has not changed; still 0) SOMETHING (?) is wrongly modifying my hardware clock; but so far, I don't know what; Sure, I could use a NTP server to set the system clock to the correct time. But definively, there is something wrong in the boot or shutdown process. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |bnc-team-screening@forge.provo.novell.com Component|Booting |Basesystem QAContact|jsrain@novell.com |qa@suse.de -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 User AmigaPhil@ping.be added comment https://bugzilla.novell.com/show_bug.cgi?id=416360#c1 --- Comment #1 from Philippe Duchenne <AmigaPhil@ping.be> 2008-08-13 10:42:00 MDT --- I haven't tried to set the clock since I wrote this report 2 days ago (I left it 30 minutes late). Today, my system clock is still 30 minutes late (no more, no less, so no other jump in time). The systematic drift rate value in /etc/adjtime is now 3.041359 seconds, which is acceptable (it was about 1 second yesterday). I still don't know what is sometimes "forcing" my clock to another time, nor why and when exactly this happen... Could it be a hardware problem ? (the hardware clock not working properly when the computer is powered off, and all starting after I installed OpenSuse 11 just being a coincidence ???) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 User AmigaPhil@ping.be added comment https://bugzilla.novell.com/show_bug.cgi?id=416360#c2 --- Comment #2 from Philippe Duchenne <AmigaPhil@ping.be> 2008-08-17 10:49:45 MDT --- My system clock seems (more or less) stable now. It's only 4 minutes late since I last synchronized it with a NTP server 3 days ago (it's not more late than yesterday). The systematic drift rate in /etc/adjtime changed from about 4 seconds, then -51 seconds, and now it is about -12 seconds. So it does not seems to be a hardware problem (Is there a way I can test that ?), but more about setting (and keeping) the right system/hardware clock in the first place. I'm going to try again a NTP sync. and see what happen in the next days. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 User AmigaPhil@ping.be added comment https://bugzilla.novell.com/show_bug.cgi?id=416360#c3 Philippe Duchenne <AmigaPhil@ping.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement --- Comment #3 from Philippe Duchenne <AmigaPhil@ping.be> 2008-08-19 12:16:28 MDT --- Still no problem with my system clock today (only 1 second late, and -0.9 as systematic drift rate). I don't know if I should close this bug report. The issue is still not resolved, it just does not happen again (I still don't know what exactly made these problems appears). Maybe a "sanity check" could be added somewhere so that, when a user is setting the clock by hand (he is supposed to enter the right time), a abnormally high systematic drift rate (such like the "-10808.673458" seconds per day I had) should be ignored and not stored. (Or something like saving the system clock to the hardware clock at the same time, without --adjust, and with a reset of the /etc/adjtime values ?) I leave this bug report open, and change the severity to "enhancement". -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mkoenig@novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=416360 User AmigaPhil@ping.be added comment https://bugzilla.novell.com/show_bug.cgi?id=416360#c4 --- Comment #4 from Philippe Duchenne <AmigaPhil@ping.be> 2008-09-16 13:50:20 MDT --- After about 1 month where my system clock was right, it is again late today (about 1 hour). I suddenly realized that after returning from a KDE4.0 session as root (I'm using the Gnome2 desktop as user). Also, I found a thread about a similar problem on the forum : http://forums.opensuse.org/install-boot-login/388755-wrong-clock-11-0-a.html... -- 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.
participants (1)
-
bugzilla_noreply＠novell.com