https://bugzilla.novell.com/show_bug.cgi?id=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c1 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |suse-beta@cboltz.de InfoProvider| |ruchir.brahmbhatt@ecosmob.c | |om AssignedTo|bnc-team-screening@forge.pr |jsuchome@suse.com |ovo.novell.com | --- Comment #1 from Christian Boltz 2012-10-15 01:27:25 CEST --- Jiří, I'm not sure if this is caused by yast2-country or the timezone package - if you think it's a bug in the timezone package, please reassign to pbaudis. Ruchir, what's the content of /etc/adjtime on your system? -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c3 Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com AssignedTo|jsuchome@suse.com |werner@suse.com --- Comment #3 from Jiří Suchomel 2012-10-15 07:49:58 UTC --- This look correct from YaST side. Anything else might be wrong? -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c5 Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |werner@suse.com --- Comment #5 from Jiří Suchomel 2012-10-15 08:59:06 UTC --- (In reply to comment #4)

If you know switch back to UTC as reference in CMOS then YaST2-country should correct /etc/adjtime first, run mkinitrd and then hwclock to be sure that both the CMOS and the kernels system time is correct after *next* boot.

How should YaST2 country correct /etc/adjtime? YaST only saves LOCAL/UTC to adjtime, based on the info given by user in the UI. And it runs mkinitrd when user changes this settings. As this seems to happened after "recent timezone update", is it likely that timezone package forgot to call mkinitrd? -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c8 Dirk Weißnich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |regi.hops@gmx.net --- Comment #8 from Dirk Weißnich 2012-10-15 20:05:34 UTC --- So there are a few bug reports on this but this one looks like the best bet on describing my problem. So first of all I have a double boot system with Windows XP and openSUSE 12.2 x86_64. Therefore I always set it up with "Hardware Clock Set as UTC" unchecked since 11.x. And it always worked til now. BTW I also synchronize the time with NTP. Now I always need to adjust the time either in Windows or in openSUSE when I changed the OS (or wait for the NTP to synchronize). Digging through the settings I find something seems to go wrong with the synchronization to the CMOS-Clock. Steps to reproduce: I set everything to the initial time in UTC STEP 1 Yast: check "Hardware Clock Set to UTC" and change time to correct local cp-m4a:~ # hwclock --debug hwclock from util-linux 2.21.2 Using /dev interface to clock. Last drift adjustment done at 1350327841 seconds after 1969 Last calibration done at 1350327841 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/10/15 19:10:45 Hw clock time : 2012/10/15 19:10:45 = 1350328245 seconds since 1969 Mon Oct 15 21:10:45 2012 -0.313614 seconds cp-m4a:~ # date Mon Oct 15 21:12:43 CEST 2012 cp-m4a:~ # cat /etc/adjtime 0.000000 1350327841 0.000000 1350327841 UTC So far everything looks good, but Windows won't see the correct time, because of UTC. ------ STEP 2 Yast: uncheck "Hardware Clock Set to UTC" and change time to correct local cp-m4a:~ # hwclock --debug hwclock from util-linux 2.21.2 Using /dev interface to clock. Last drift adjustment done at 1350328443 seconds after 1969 Last calibration done at 1350328443 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/10/15 19:15:03 Hw clock time : 2012/10/15 19:15:03 = 1350321303 seconds since 1969 Mon Oct 15 19:15:03 2012 -0.579241 seconds cp-m4a:~ # date Mon Oct 15 21:16:56 CEST 2012 cp-m4a:~ # cat /etc/adjtime 0.000000 1350328443 0.000000 1350328443 LOCAL mkinitrd was also called from yast: Oct 15 21:14 initrd-3.4.11-2.16-desktop As you can see the CMOS-Clock wasn't set to the correct time which should be now local! ------ STEP 3 Also a reboot doesn't change anything REBOOT BIOS shows wrong time, so the change wasn't synched back to CMOS cp-m4a:~ # date Mon Oct 15 19:20:03 CEST 2012 cp-m4a:~ # hwclock --debug hwclock from util-linux 2.21.2 Using /dev interface to clock. Last drift adjustment done at 1350328443 seconds after 1969 Last calibration done at 1350328443 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/10/15 19:20:09 Hw clock time : 2012/10/15 19:20:09 = 1350321609 seconds since 1969 Mon Oct 15 19:20:09 2012 -0.360438 seconds ------ STEP 4 REBOOT Setting the right time in BIOS cp-m4a:~ # date Mon Oct 15 21:27:31 CEST 2012 cp-m4a:~ # hwclock --debug hwclock from util-linux 2.21.2 Using /dev interface to clock. Last drift adjustment done at 1350328972 seconds after 1969 Last calibration done at 1350328972 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/10/15 21:27:36 Hw clock time : 2012/10/15 21:27:36 = 1350329256 seconds since 1969 Mon Oct 15 21:27:36 2012 -0.251077 seconds ------ And the other wired thing is that Yast always warns me when I uncheck the "Hardware Clock Set to UTC" that it doesn't find any other OS(!?) and I should set UTC because else DST won't work - never saw this warning before 12.2. I hope somebody can look into it and find out what's wrong. Thanks Dirk -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c10 --- Comment #10 from Dr. Werner Fink 2012-10-17 08:58:07 UTC --- Please use hwclock --debug --test to avoid to write and modify to your HW clock. To see the real system clock use TZ=UTC date as this shows always the clock used by the kernel. This clock has to be always in UTC otherwise network and user space time are wrong! The date command and any other command without TZ=UTC will show local time as the glibc API will use then /etc/localtime to convert the system time into local time. Please check if the initrd boot image has the appropiate files around: lsinitrd -l /boot/initrd | grep -E 'clock|time|UTC' Then check if /etc/adjtime use the same time reference on disk as well as in the initrd: zcat /boot/initrd | cpio -i --to-stdout --quiet etc/adjtime | tail -n 1 tail -n 1 /etc/adjtime zcat /boot/initrd | cpio -i --to-stdout --quiet etc/localtime | cmp - /etc/localtime And if the kernels system clock was corrected test -e /dev/shm/warpclock || echo system clock not warped ... -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c12 --- Comment #12 from Dirk Weißnich 2012-10-18 19:38:30 UTC --- Created an attachment (id=510107) --> (http://bugzilla.novell.com/attachment.cgi?id=510107) initrd log after enabling local timezone -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c14 --- Comment #14 from Dirk Weißnich 2012-10-18 19:41:32 UTC --- Hi Werner, first of all thanks for the quick reply. I did all the checks you mentioned and attached 2 files. timeproblem.txt contains the results to not bloat this bug report. First run with UTC Second after enabling local timezone What I also recognized, after enabling local timezone there was also a file /dev/shm/warpclock with 0 bytes Another thing is that the number in the drift file /var/lib/ntp/drift/ntp.drift increases strangely high. On 15. Oct it shows approx. 1.5, today it shows 4.323, but with openSUSE 12.1 it was always around 0.5 on the same hardware. For now I set everything to UTC as openSUSE is my main OS, if Windows shows the wrong time it doesn't hurt me so much ;-) But it's strange - does the time handling changed from 12.1 to 12.2? Regards Dirk -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #510107|application/octet-stream |text/plain mime type| | -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c17 Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jsuchome@suse.com | --- Comment #17 from Jiří Suchomel 2012-10-19 12:18:46 UTC --- If user just switches to local time in YaST, it means that /etc/adjtime is changed (3rd line to LOCAL) and mkinitrd is called. There is special ocasion, when "/sbin/hwclock --systohc" is called, but this is only when current (system) time was directly synchronized from NTP. -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c19 --- Comment #19 from Jiří Suchomel 2012-10-22 06:09:17 UTC --- (In reply to comment #18)

Do you mean the option in YaST where you can choose to change date and time manually or via NTP? Then it definitely does not work, cause there I tried it already.

We can look into YaST logs if you have them, this situation should be logged. -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c21 --- Comment #21 from Dirk Weißnich 2012-10-25 19:24:51 UTC --- Created an attachment (id=510944) --> (http://bugzilla.novell.com/attachment.cgi?id=510944) y2log - Local to UTC YaST Log changing timezone from local to UTC, synchronizing with NTP -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c23 --- Comment #23 from Jiří Suchomel 2012-10-26 06:09:50 UTC --- (In reply to comment #22)

Hi Jiri,

I attached 2 Parts of the YaST-Log. I bootet the machine with BIOS time set to UTC. Then I changed to local time via YaST

This seems to be wrong. YaST is not intended to change the time format you hold in BIOS. It actually tells the system, what you have there. So if you know BIOS uses UTC, set UTC in YaST. If (and only if) you know there's local time in BIOS, set Local time in YaST. -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c25 --- Comment #25 from Dirk Weißnich 2012-10-31 23:19:17 UTC --- Another test slightly different: I presume BIOS is set to UTC: 1. After boot login to KDE 2. Start YaST and change to local time, you will see the change immediately in the clock field next to the checkbox 3. Click on change and set the time MANUALLY to local time 4. Reboot 5. Login to KDE and you will see the correct time 6. Reboot 7. Login to KDE the time is still correct 8. Wait long enough to let NTP do his job (at least 30 minutes) 9. Reboot and look into the BIOS the time was changed to local time

From now on it seems that local time is working.

And now for the final action that mess up everything again: 10. Start YaST and open Date and Time settings 11. Click on change (next to the time) 12. Activate NTP (on my system it was already activated) 13. Click "Synchronize Now" 14. Save and close YaST 15. reboot 16. The Time is wrong again For me it seems that the "Synchronize Now" - action does not respect the time zone settings and always synch to UTC and ALSO change the BIOS Clock, cause after a reboot i checked and the BIOS time was set back to UTC. Cheers Dirk -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c27 --- Comment #27 from Dirk Weißnich 2012-11-07 20:40:28 UTC --- (In reply to comment #26) Yes - I checked /etc/adjtime throughout my tests and it was always set to the right zone by YaST. I suspect there is not only one bug (may a combination), but something is wrong with "sntp" or whatever is called when you press the button "Synchronize Now". Cause if you managed to get local time working for a while and you call "rcntp ntptimeset" which calls "sntp", the BIOS time is set back to UTC and after a reboot time is messed up again. Did you tried the steps I described above? -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c29 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #29 from Wolfgang Bauer 2013-01-07 12:19:04 UTC --- I think this is a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=791106 Could you please try the workaround listed there? (NTPD_FORCE_SYNC_ON_STARTUP can be found in /etc/sysconfig/ntp) -- 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=783853 https://bugzilla.novell.com/show_bug.cgi?id=783853#c31 --- Comment #31 from Wolfgang Bauer 2013-01-28 14:08:29 UTC --- Well, in the meantime there is an online update in progress for bnc#791106! So I guess this bug can be closed. Now there's only bnc#791485 left to be fixed regarding localtime I think. ;-) -- 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.