Red Hat Bugzilla – Bug 249981
Clock gets borked after upgrade to 184.108.40.206-33.fc7
Last modified: 2007-11-30 17:12:11 EST
Description of problem:
After upgrade to 220.127.116.11-33.fc7 version of kernel my clock gets borked. For
some reason the date as seen by syslog entries are timestamped all the time with
exactly the same date! It is also some bogus date (not like +1h but like
+2h23m). I've experienced it in syslog and in other userland programs like ekg.
The date command however gives proper time.
I can confirm this on my 3-year-old system, i686, AMD Athlon XP 2800+, nForce
Chipset, Asus A7N8X-Deluxe mobo/bios (for whatever it matters). Uptime reports
the wrong time, still the uptime counter appears to be correct.
I wish to add that after passing the "bogus time", the gnome clock appears to be
running normally again. Probably until the next reboot. In my case the
difference between the bogus time and the real time was 2 hours directly after
booting, the difference between GMT and British Summer Time +1 (my timezone,
Dupe of bug 249942?
More dupe of https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249857, see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249857#c13 for an
*** This bug has been marked as a duplicate of 249857 ***
same probleme here on my Asus M2N-E with nForce chipset. And with this kernel my
nic can't get a dhcp address anymore (don't know if it's related but it was
working fine with previous kernel)
In my case, the bogus time only appears in Gnome (since gdm login screen). In a
term date is ok.
Also if i close my session i've got the error message saying that my session has
lasted less than 3 (not sure) seconds.