http://bugzilla.novell.com/show_bug.cgi?id=595573 http://bugzilla.novell.com/show_bug.cgi?id=595573#c0 Summary: Wrong hardware date after Daylight Saving ended: Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gfarrell@netspeed.com.au QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.2) Gecko/20100317 SUSE/3.6.2-1.2 Firefox/3.6.2 Australia's Eastern Daylight Time (AEDT) reverted to Australian Eastern Standard Time (AEST) at 0300 AEDT on Sun 04 April 2010. While the System time on my computer seemed to be updated (time shown in the notification area, and output of the 'date' command), there were inconsistencies in the logs. Also, the Hardware time set in the BIOS remained one hour ahead (ie, still set to AEDT). The /var/log/messages output shows the successful transition to AEST at 0300 AEDT (becoming 0200 AEST): .. Apr 4 02:59:20 Linuxbox kernel: [968309.297164] martian source 255.255.255.255 from 10.3.246.120, on dev eth1 Apr 4 02:59:20 Linuxbox kernel: [968309.297187] ll header: ff:ff:ff:ff:ff:ff:00:a0:fa:03:f6:79:08:00 Apr 4 02:59:40 Linuxbox kernel: [968329.293682] martian source 255.255.255.255 from 10.3.246.120, on dev eth1 Apr 4 02:59:40 Linuxbox kernel: [968329.293701] ll header: ff:ff:ff:ff:ff:ff:00:a0:fa:03:f6:79:08:00 ----------------------------------- Transition occurred here ----------------------------------- Apr 4 02:01:16 Linuxbox smartd[2532]: Device: /dev/sdc [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 112 to 110 Apr 4 02:01:16 Linuxbox smartd[2532]: Device: /dev/sdc [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 63 to 64 Apr 4 02:05:21 Linuxbox kernel: [968670.241099] martian source 255.255.255.255 from 10.3.246.120, on dev eth1 Apr 4 02:05:21 Linuxbox kernel: [968670.241118] ll header: ff:ff:ff:ff:ff:ff:00:a0:fa:03:f6:79:08:00 .. However, re-boots showed sudden changes in time at about the moment that bootup is completed (just after ntpd is activated??): .. Apr 11 09:59:57 Linuxbox kernel: [ 36.812358] Slow work thread pool: Starting up Apr 11 09:59:57 Linuxbox kernel: [ 36.812491] Slow work thread pool: Ready Apr 11 09:59:57 Linuxbox kernel: [ 36.812575] FS-Cache: Loaded Apr 11 09:59:57 Linuxbox kernel: [ 36.909638] FS-Cache: Netfs 'nfs' registered for caching ----------------------------------- The above times are one hour ahead of AEST. Note the sudden wind-back of one hour to the correct time at this point ----------------------------------- Apr 11 09:00:19 Linuxbox python: hp-systray[3485]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting. Apr 11 09:19:43 Linuxbox rsyslogd: -- MARK -- Apr 11 09:20:32 Linuxbox su: (to root) geoff on /dev/pts/0 Apr 11 09:26:40 Linuxbox shutdown[11471]: shutting down for system reboot .. Another from /var/log/warn: Apr 4 11:06:24 Linuxbox nmbd[2008]: query_name: Failed to send packet trying to query name WORKGROUP<1d> Apr 4 11:06:28 Linuxbox kernel: [ 26.557455] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Apr 4 11:06:32 Linuxbox smartd[2702]: Device: /dev/sdc [SAT], 1 Currently unreadable (pending) sectors Apr 4 11:06:32 Linuxbox smartd[2702]: Device: /dev/sdc [SAT], 1 Offline uncorrectable sectors ----------------------------------- The above times are one hour ahead of AEST. Note the sudden wind-back of one hour to the correct time at this point ----------------------------------- Apr 4 10:06:51 Linuxbox python: hp-systray[3398]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting. Apr 4 10:36:32 Linuxbox smartd[2784]: System clock time adjusted to the past. Resetting next wakeup time. Apr 4 11:06:32 Linuxbox smartd[2784]: Device: /dev/sdc [SAT], 1 Currently unreadable (pending) sectors Apr 4 11:06:32 Linuxbox smartd[2784]: Device: /dev/sdc [SAT], 1 Offline uncorrectable sectors (smartd noticed this at Apr 4 10:36:32 and adjusted for the change.) This has occurred at every bootup since Daylight Saving ended. I rebooted and found the Hardware time in the BIOS was one hour ahead. It had not been updated, as expected by the procedure in /etc/init.d/boot.clock that saves System time to Hardware time at shutdown. This should have occurred on the first shutdown conducted on 04 April 2010. It's obvious that it didn't occur then, and hasn't since. Since manually changing the Hardware time to AEST in the BIOS, the sudden changes in time have not occurred. A further curiosity is seen in /var/log/boot.msg: <6>[ 1.999154] rtc_cmos 00:04: setting system clock to 2010-04-11 09:29:09 UTC (1270978149) At the time this line was logged, UTC time was 2010-04-10 23:29:09 in my UTC +10 time zone. My /etc/sysconfig/clock settings are: HWCLOCK="--localtime" SYSTOHC="yes" TIMEZONE="Australia/Sydney" DEFAULT_TIMEZONE="US/Eastern" Having correct handling of the System time is important, as I have been having NFS problems since Daylight Saving ended, where connections have been sporadic. To correct these problems, I have had to go into YaST-> Network Services-> NFS Server and re-process the settings each time. Since manually correcting the Hardware time in the BIOS, the NFS connection problems have disappeared. Reproducible: Always Steps to Reproduce: 1. After Daylight Saving has ended, start the computer. 2. Then re-boot it. Actual Results: The Hardware clock in the BIOS is still set to one hour ahead Expected Results: The Hardware clock should have changed to one hour behind Daylight Saving time. Considered Major because of the effect on NFS. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.