| Summary: | clock does not obey System clock uses UTC setting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Hampton <error> | ||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 9 | CC: | aros, harald, jik, notting, nphilipp, rvokal | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-07-15 08:25:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 451175 | ||||||
| Attachments: |
|
||||||
|
Description
Michael Hampton
2008-05-16 23:38:29 UTC
What does your /etc/adjtime file look like? Do you have any rtc devices in /sys/class/rtc? error@roam ~/Desktop $ cat /etc/adjtime -0.000794 1211654886 0.000000 1211654886 LOCAL error@roam ~/Desktop $ cat /sys/class/rtc/rtc0/device/id PNP0b00 Your configuration is wrong... the last line of /etc/adjtime needs to be UTC for it to be treated as UTC. Is system-config-date not updating the file correctly? My system BIOS clock is set to LOCAL time, not UTC. (One of the hazards of dual booting Windows.) But the system seems to be assuming UTC when I start it up, as the Linux system clock comes up four hours behind the correct time. It seems that s-c-date isn't pertinent to this bug. In that case, I'll pass it back. Sorry, I misread the subject. What happens (once it's booted 'wrong') if you do 'echo "add" > /sys/class/rtc/rtc0/uevent') ? This is what happens: error@roam ~ $ su - Scan right index finger on UPEK TouchStrip root@roam ~ # echo "add" > /sys/class/rtc/rtc0/uevent root@roam ~ # echo $? 0 root@roam ~ # cat /sys/class/rtc/rtc0/uevent MAJOR=254 MINOR=0 root@roam ~ # Though, I must admit, the system mysteriously is booting up with the correct local time now, without having to manually correct the clock. Again, I have no idea why, or what was wrong before, or why it works now. But, at least, it seems to be working. When it was failing, were you booting a significantly older kernel? Yes, I was booting my backup kernel from Fedora 8 (2.6.24.4-64.fc8) while I was trying to work out an unrelated F9 kernel problem. Created attachment 307073 [details]
patch for this issue
Ah, the F8 kernel isn't using the RTC class device, so it's hitting the old
compat code in the udev rule... which is broken.
Try the attached with a Fedora 8 kernel.
*** Bug 438100 has been marked as a duplicate of this bug. *** Bill, your patch 307073 seems to have fixed the problem; I booted up on 2.6.24.4-64.fc8 and the clock came up with the correct time. Thanks! initscripts-8.76.3-1 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/initscripts-8.76.3-1 initscripts-8.76.3-1 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update initscripts'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-7667 initscripts-8.76.3-1 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 451175 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |