[Bug 495417] New: boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days) - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 493877] New: kickoff: in...

[Bug 495417] New: boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

older
[Bug 487060] 11.2 Alpha0 x86_64...

bugzilla_noreply＠novell.com

16 Apr 2009 16 Apr '09

06:24

http://bugzilla.novell.com/show_bug.cgi?id=495417 Summary: boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days) Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de Found By: --- Created an attachment (id=286025) --> (http://bugzilla.novell.com/attachment.cgi?id=286025) /etc/adjtime as found on the system after the clock was set once again User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081213 SUSE/1.1.14-1.1 SeaMonkey/1.1.14 When the hardware clock (RTC chip) ever got the time incorrectly, and you set the time correctly in Linux, the clock goes completely crazy. For examply when the clock was correct before booting openSUSE, the clock is two days behind when boot is complete. Reproducible: Always Steps to Reproduce: 1. Use some software (e.g. a live CD that assumes a different timezone than you live in, and your RTC is set to local time (usual for a dual-boot system) 2. Boot openSUSE to find out that the time is incorrect. Use "date -s" to set the time correctly (as root) 3. Reboot 4. Boot openSUSE again, maybe after a few days Actual Results: The time is completely wrong (several hours or days) Expected Results: As the time was correctly set, the time should be correct. The design, specifically of "hwclock --adjust" is completely broken, because it assumes that no other program is setting the clock. For a dual-boot system this assumption does not hold, and it does not hold when NTP is used to set the time. Despite of that is the range in which hwclock adjusts the time completely idiotic: If someone actually sells a clock chip that is wrong by more than a minute per day (almost 695 PPM), it's not a clock chip, and it should be dumped (NTP quits if the error is more than about 500 PPM). Today's wrist watches have an error of less than 3 seconds per day, most of them only about one second per day (12-35 PPM). Now if hwclock adjusts the clock about eight hours per day (about 300000PPM), that's completely free of any commonsense; if it adjusts the time back by more than a day within one boot (the clock was set to the correct time in Windows/XP when it was found to be wrong), that's completely idiotic. -- 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.

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

16 Apr 16 Apr

08:21

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |ro@novell.com |ovo.novell.com | -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:45

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #286025|application/octet-stream |text/plain mime type| | -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:48

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c2 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensb | |urg.de --- Comment #2 from Dr. Werner Fink 2009-04-16 02:48:00 MDT --- I'd like to know who has created this /etc/adjtime as the script /etc/init.d/boot.clock does this *only* for UTC based CMOS clocks! -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:35

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

From the date of the file (I'll have to re-validate to be sure) I'd say it was created/updated during boot. Does comment #2 mean the file is not CREATED unless the RTC runs UTC, or does it mean it's not UPDATED unless the clock runs UTC? Meaning: If the file exists, it it updated regardless of the timezone of

http://bugzilla.novell.com/show_bug.cgi?id=495417 User Ulrich.Windl@rz.uni-regensburg.de added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c3 Ulrich Windl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Ulrich.Windl@rz.uni-regensb | |urg.de | --- Comment #3 from Ulrich Windl 2009-04-16 13:35:58 CEST --- the RTC? Seeing the code I guess: "no", but something is very odd there. I had to fix the system time several times in the last days. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:36

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c4 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WORKSFORME --- Comment #4 from Dr. Werner Fink 2009-04-16 07:36:15 MDT --- The /etc/adjtime is only created if and only if CMOS clock runs in UTC. For your problem please simply remove the left over /etc/adjtime and set SYSTOHC in /etc/sysconfig/clock to "no" then the System Time is never used to set the HW CMOS clock. Please if you find any other program around which might create an /etc/adjtime then reopen this bug. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17 Apr 17 Apr

20:07

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User holler@nefkom.info added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c5 Hans-Peter Holler changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Version|Final |Factory Component|Basesystem |Basesystem CC| |holler@nefkom.info AssignedTo|werner@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Resolution|WORKSFORME | Product|openSUSE 11.0 |openSUSE 11.2 OS/Version|openSUSE 11.0 |SuSE Other --- Comment #5 from Hans-Peter Holler 2009-04-17 14:07:13 MDT --- Werner: Sorry for reopening and hijacking, but maybe this is the fastest way :-) rpm -q aaa_base-11.2-19.1 -changelog * Do Apr 16 2009 werner@suse.de - Make boot.clock more tough due udev timings (bnc#492921) - Remove /etc/adjtime in boot.clock if left over (bnc#495417) bnc#492921 isn't public, but maybe the explanation for the two hour time shift on boot _before_ /etc/init.d/boot.clock is run after today's factory updates can be found there. What are these "udev timings", mentioned in the changelog? My / my computer's problem: On boot system _and_ hardware time is incremented +2 hours: Extract from /var/log/boot.msg: Kernel log daemon terminating. Boot logging started on /dev/char/../tty1(/dev/console) at Fri Apr 17 18:01:09 2009 Trying manual resume from /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part3 Invoking userspace resume from /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part3 resume: libgcrypt version: 1.4.1 Trying manual resume from /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part3 Invoking in-kernel resume from /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part3 Waiting for device /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part4 to appear: ok fsck 1.41.4 (27-Jan-2009) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part4 /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part4: clean, 372945/6103040 files, 13687185/24384661 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part4 mount -o rw,defaults -t ext3 /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE8717-part4 /root boot/91-killudev.sh: line 17: kill: (614) - No such process Boot logging started on /dev/char/../tty1(/dev/console (deleted)) at Fri Apr 17 20:01:12 2009 done got request to load boot.udev 4 got request to load startpar 5 startpar not found Server closed connection Starting udevd: done Loading drivers, configuring devices: done got request to load boot.loadmodules 4 boot.loadmodules not found Loading required kernel modules doneActivating swap-devices in /etc/fstab... doneStart of /etc/init.d/boot.clock System Time is Fri Apr 17 20:01:16 CEST 2009 System Time is Fri Apr 17 20:01:16 CEST 2009 The System Time is already in sync with Hardware Clockunused Please have a look at the lines "Boot logging started on ...". You will see the two hours difference. The extra lines "Start of /etc/init.d/boot.clock System Time is Fri Apr 17 20:01:16 CEST 2009 System Time is Fri Apr 17 20:01:16 CEST 2009" come from /etc/init.d/boot.clock tweaked by me. I have no clue what happens between these "Boot logging started on ..." lines. As you can see these lines are written before /etc/init.d/boot.clock is run. Wild guess for the two hours: UTC +1 for Germany/Berlin +1 for summertime. No /etc/adjtime. /etc/sysconfig/clock: ## Path: System/Environment/Clock ## Description: Information about your timezone and time ## Type: string(-u,--utc,--localtime) ## ServiceRestart: boot.clock # # Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime" ## Description: Write back system time to the hardware clock ## Type: yesno ## Default: yes # # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # SYSTOHC="no" ## Type: string(Europe/Berlin,Europe/London,Europe/Paris) ## ServiceRestart: boot.clock # # Timezone (e.g. CET) # (this will set /usr/lib/zoneinfo/localtime) # TIMEZONE="Europe/Berlin" DEFAULT_TIMEZONE="Europe/Berlin" Hopefully you are able to reproduce this and know the one (you?) who could resolve this. Thanks in advance. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18 Apr 18 Apr

20:19

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User holler@nefkom.info added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c6 Hans-Peter Holler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com --- Comment #6 from Hans-Peter Holler 2009-04-18 14:19:24 MDT --- http://lists.opensuse.org/opensuse-commit/2009-04/msg00340.html +Fri Apr 17 18:58:53 CEST 2009 - werner@xxxxxxx + +- boot.clock: write system time only back to HW clock if kernel + time status shows that clocks are unsynchronized +- Add two helper scripts for mkinitrd to add and load rtc_cmos + module and add /etc/localtime to initrd (bnc#492921) Again a reference to the non public bnc#492921. Stephan? -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

20:21

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 Hans-Peter Holler changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |werner@novell.com |ovo.novell.com | -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

20 Apr 20 Apr

12:21

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c7 --- Comment #7 from Stephan Kulow 2009-04-20 06:20:59 MDT --- Can't help, the bug contains sensitive informations about the machine used and I don't dare to publish them. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

12:48

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User Ulrich.Windl@rz.uni-regensburg.de added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c8 --- Comment #8 from Ulrich Windl 2009-04-20 14:48:54 CEST --- On comment #4: I wondered where during system shutdown the RTC clock is updated; boot.clock has an empty "stop" action. As in the absence of NTP no body ever updates the RTC chip if the kernel time was set, the obvious latest possibility is before rebooting. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:18

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c9 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |WORKSFORME --- Comment #9 from Dr. Werner Fink 2009-04-20 07:18:32 MDT --- For factory I've done the following changes before I've logged in and read this reopened bugzilla: Mon Apr 20 14:50:34 CEST 2009 - werner@suse.de - boot.clock: make status argument work and add argument timezone - boot.clock: for s390 make date command accurate as possible - Rename mkinitrd script setup-rtc.sh to setup-clock.sh and add boot-clock.sh, also check for including boot-rtc.sh the existence of the rtc_cmos module to avoid fatal errors Fri Apr 17 18:58:53 CEST 2009 - werner@suse.de - boot.clock: write system time only back to HW clock if kernel time status shows that clocks are unsynchronized - Add two helper scripts for mkinitrd to add and load rtc_cmos module and add /etc/localtime to initrd (bnc#492921) the last change to avoud the udev timings (read the fine manual page) are not public for openSuSE 11.1 nor for SLES11. This changes makes no sence for openSuSE 11.1 nor for SLES11 as the adjtimex is located on /usr/sbin and not on /sbin/ and also the udevadm isn't new enough to know about ``settle --quiet --seq-start=$start --seq-end=$end'' Beside this for openSuSE 11.0 and only for 11.0 the correct script to run stop is boot.getclock. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21 Apr 21 Apr

14:08

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c10 --- Comment #10 from Dr. Werner Fink 2009-04-21 08:08:25 MDT --- Created an attachment (id=287137) --> (http://bugzilla.novell.com/attachment.cgi?id=287137) /etc/init.d/boot.clock The /etc/init.d/boot.clock I use on openSuSE 11.1 ... please note that this works only if /usr is part of the root file system, otherwise one see an error like /etc/init.d/boot.clock: adjtimex: command not found For 11.1 I've moved /usr/sbin/adjtimex to /sbin/ and I'm using the new options --quiet,--seq-start=, and --seq-end= of `udevadm settle' -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19:54

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User holler@nefkom.info added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c11 --- Comment #11 from Hans-Peter Holler 2009-04-21 13:54:06 MDT --- Hi, with aaa_base-11.2-21.1 from today's Factory _my_ problem is gone :-) Seems to be the missing parts in initrd, so rpm -Fhv aaa_base-11.2-21.1.i586.rpm; mkinitrd; init 6 resolved the 2+ hours issue. Many Thanks. Ulrich: your bug was originally created against 11.0, I changed it to 11.2 Alpha 0/Factory, Werner mentions 11.1 in comment #10. What about _your_ problem? All: sorry for the mess. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

22 Apr 22 Apr

06:30

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User Ulrich.Windl@rz.uni-regensburg.de added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c12 --- Comment #12 from Ulrich Windl 2009-04-22 08:30:19 CEST --- Meanwhile I had my 11.0 system updated to 11.1 (plus all updates), and I found another interesting "feature" during boot: The time is correct, then off by two hours (UTC offset?), then correct again. That can bee seen through "grep started /var/log/boot.msg": Boot logging started on /dev/tty1(/dev/console) at Tue Apr 21 21:52:00 2009 Boot logging started on /dev/tty1(/dev/console (deleted)) at Tue Apr 21 23:52:03 2009 Boot logging started on /dev/tty1(/dev/console) at Tue Apr 21 21:52:30 2009 (21:52 is the correct time of day, RTC runs local time) Also viewable through "last": windl pts/1 Tue Apr 21 21:55 still logged in windl pts/0 Tue Apr 21 21:55 still logged in windl :0 console Tue Apr 21 21:55 still logged in windl :0 Tue Apr 21 21:55 - 21:55 (00:00) root tty1 Tue Apr 21 21:53 still logged in reboot system boot 2.6.27.21-0.1-pa Tue Apr 21 23:52 (-1:-55) root tty1 Mon Apr 20 23:18 - 00:06 (00:48) windl pts/1 Mon Apr 20 22:57 - 23:18 (00:20) windl pts/0 Mon Apr 20 22:57 - 23:18 (00:20) windl :0 console Mon Apr 20 22:57 - 23:18 (00:20) windl :0 Mon Apr 20 22:57 - 22:57 (00:00) root tty1 Mon Apr 20 22:36 - 22:57 (00:21) reboot system boot 2.6.27.21-0.1-pa Tue Apr 21 00:32 (00:-25) root tty1 Mon Apr 20 21:23 - 21:27 (00:04) reboot system boot 2.6.25.20-0.1-pa Mon Apr 20 23:22 (-1:-54) root tty1 Sun Apr 19 18:50 - 17:48 (22:58) reboot system boot 2.6.25.20-0.1-pa Sun Apr 19 20:49 (20:59) On comment #11: For 11.0 (and 11.1?) one of the problems is that when root sets the time via command line (date -s), the RTC is not updated during a clean shutdown, even though the "$SYSTOHC" feature is set. This in turn may badly interact with the "adjust" feature of hwclock (iven if that shouldn't be used at all if the RTC runs local time (as for me)) -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:50

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c13 --- Comment #13 from Dr. Werner Fink 2009-04-22 02:50:58 MDT --- The kernel *always* assumes that RTC is in UTC (common in UNIX world) ... that is that after the kernel had set the System Time accordingly to RTC you'll will see an offset due the zone defined in /etc/localtime .. after boot.clock has done its jobs this is corrected. -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

12:33

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User Ulrich.Windl@rz.uni-regensburg.de added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c14 --- Comment #14 from Ulrich Windl 2009-04-22 14:33:16 CEST --- Does comment #13 really explain why the clock during boot is first correct, then wrong, then correct again (See boot.msg)? The reboot entry for last is written by init (I guess), right after initrd finished. Shouldn't the time be corrected already then? The kernel not being able to handle the RTC's time zone is a weak excuse, especially as I've solved the problem years ago (See http://www.eecis.udel.edu/~ntp/ntpfaq/NTP-s-trouble.htm#Q-LINUX-CMOS-UTC). -- 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.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

12:36

New subject: [Bug 495417] boot.clock (hwclock --adjust) broken by design (clock "corrected" several hours/days)

http://bugzilla.novell.com/show_bug.cgi?id=495417 User werner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495417#c15 --- Comment #15 from Dr. Werner Fink 2009-04-22 06:36:22 MDT --- There was a lot of changes during your URL

cat /proc/sys/kernel/time cat: /proc/sys/kernel/time: No such file or directory

-- 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.

Reply

Sign in to reply online Use email software

5493

Age (days ago)

5499

Last active (days ago)

Download

17 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com