Mailinglist Archive: opensuse-bugs (9626 mails)
| < Previous | Next > |
[Bug 339025] New: hwclock -w is wrong two times a year
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 5 Nov 2007 01:08:55 -0700 (MST)
- Message-id: <bug-339025-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=339025
Summary: hwclock -w is wrong two times a year
Product: openSUSE 10.2
Version: Final
Platform: i586
OS/Version: openSUSE 10.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: jborries@xxxxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Other
CMOS clock is on local time.
cron runs ntpdate every two days.
cron runs "hwclock -w" every week.
The system is running round the clock year after year.
When local time jumps from Middle European Summertime to Middle European Time
(or back a half year later) "hwclock -w" shows something like this:
hwclock from util-linux-2.12r
Using /dev/rtc interface to clock.
Last drift adjustment done at 1193528582 seconds after 1969
Last calibration done at 1193528582 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: 2007/11/04 01:45:14
Hw clock time : 2007/11/04 01:45:14 = 1194137114 seconds since 1969
Time elapsed since reference time has been 0.934735 seconds.
Delaying further to reach the next full second.
Setting Hardware Clock to 00:45:02 = 1194133502 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Clock drifted -3600.0 seconds in the past 604919 seconds in spite of a drift
factor of -1.710163 seconds/day.
Adjusting drift factor by -511.134618 seconds/day
--
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.
Summary: hwclock -w is wrong two times a year
Product: openSUSE 10.2
Version: Final
Platform: i586
OS/Version: openSUSE 10.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: jborries@xxxxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Other
CMOS clock is on local time.
cron runs ntpdate every two days.
cron runs "hwclock -w" every week.
The system is running round the clock year after year.
When local time jumps from Middle European Summertime to Middle European Time
(or back a half year later) "hwclock -w" shows something like this:
hwclock from util-linux-2.12r
Using /dev/rtc interface to clock.
Last drift adjustment done at 1193528582 seconds after 1969
Last calibration done at 1193528582 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: 2007/11/04 01:45:14
Hw clock time : 2007/11/04 01:45:14 = 1194137114 seconds since 1969
Time elapsed since reference time has been 0.934735 seconds.
Delaying further to reach the next full second.
Setting Hardware Clock to 00:45:02 = 1194133502 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Clock drifted -3600.0 seconds in the past 604919 seconds in spite of a drift
factor of -1.710163 seconds/day.
Adjusting drift factor by -511.134618 seconds/day
--
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.
| < Previous | Next > |