Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: after resuming from hibernation the system time is always wrong. Usually it stays at the time of hibernation, however I also had cases where it jumped a couple of years into the future. Version-Release number of selected component (if applicable): I do not know which component is actually responsible, I had this problem from the beginning after installing Fedora 20. Currently I am on kernel 3.14.2-200.fc20.x86_64, ntpdate-4.2.6p5-18.fc20.x86_64, ntp-4.2.6p5-18.fc20.x86_64 I actually do not think that this is an ntp problem, but I am not sure who is responsible for the system clock when hibernating/resuming. How reproducible: Hibernate in the evening, resume in the morning - observe that your system time is wrong. Steps to Reproduce: 1. note which time it is and hibernate 2. wait a while and note how long you waited 3. resume and check the current time of the system Actual results: Time is wrong. Expected results: Time should be correct :) Additional info: I have to manually do a service ntpd restart after resuming in order to fix my time. The service as such is actually enabled. Please let me know if you need some specific logs or if you need me to do some tests or whatever. Thank you.
This looks like a problem in the kernel or HW.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
I keep my system up to date and I am already running 3.14.4-200.fc20.x86_64, unfortunately the problem is still there.
I have the same problem with kernel 3.15.7
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
I still have the problem with kernel 3.17.2
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
Still have the same problem on Fedora 21 / 3.18.6-200.fc21.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
have similar bug... I'm experiencing strange issue with resuming from suspend to RAM (sleep). When the system is put to sleep and resumed, the clock/date/time is shifted 2 days and 20 hours into the future fedora-22 uptodate... it whas the same with fedora-21... 1year ago
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.