Hide Forgot
Description of problem: during boot sequence clock is set 8 hours ahead of actual local time Version-Release number of selected component (if applicable): systemd-29-1.fc16.x86_64 How reproducible: every time Steps to Reproduce: 1. boot rawhide 2. see that clock is 8 hours ahead in gnome-shell 3. Actual results: clock 8 yours ahead Expected results: clock at correct local time Additional info: This may not be systemd and may be same as: https://bugzilla.redhat.com/show_bug.cgi?id=672194 "hwclock --systz" sets the wrong time when hw clock tracks localtime # cat /sys/class/rtc/rtc0/hctosys 1 # hwclock --show --debug hwclock from util-linux 2.19.1 Using /dev interface to clock. Last drift adjustment done at 1310390045 seconds after 1969 Last calibration done at 1310390045 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: 2011/07/11 12:36:26 Hw clock time : 2011/07/11 12:36:26 = 1310402186 seconds since 1969 Mon 11 Jul 2011 12:36:26 PM EDT -0.611447 seconds # tail -1 /etc/adjtime LOCAL # echo TZ America/New_York # zdump /etc/localtime /etc/localtime Mon Jul 11 20:36:26 2011 EDT # date Mon Jul 11 20:36:26 EDT 2011 Have to use gnome Date and Time app to manually set clock to correct local time. BIOS time is set to local time. Time is correct on this machine when booting Fedoras 13, 14, and 15. Setting severity to high since wrong time impacts yum updates and also causes filesystem checks to see future dates.
Can you please boot with "systemd.log_level=debug" and "systemd.log_target=kmsg"? and paste the output of "dmesg" after boot here?
Created attachment 513685 [details] dmesg output requested As requested.
Clock now being set 4 hours ahead vice 8. Don't know what led to this change.
Hmm, so this is weird. systemd should log a message like "RTC configured in localtime, applying delta of %i minutes to system time" when it applies the local RTC offset. This message does not appear in your output. Can you retry this with the current version of systemd from f16, and see if you can reproduce this issue? Do you see this log message then?
Sorry, had to reinstall and the issue is resolved with a reinstall. So, probably I exacerbated the original problem with some poor hacking on my part when the problem first appeared. Thank you for looking at this. Closing now--Insufficient Data, I guess. Regards, OldFart