Lastnight did an update to my computer to kernel 220.127.116.11-33.fc7 and rebooted. Following the reboot my desktop clock in both GNOME and XFCE4
seemed to get stuck and not proceed forward.
If I issued the date command from a terminal the time seemed correct.
The /var/log/messages file contained the frozen time stamp also
Aug 1 18:13:08 blackbox syslogd 1.4.2: restart.
Aug 1 18:13:08 blackbox kernel: klogd 1.4.2, log source = /proc/kmsg started.
Aug 1 18:13:08 blackbox kernel: Linux version 18.104.22.168-33.fc7 (kojibuilder@xenb
..... Many lines of logging with exact same timestamp .........
Aug 1 18:13:08 blackbox NetworkManager:
Rebootting back into the older kernel (22.214.171.124-27.fc7) fixed the problem. Notice how the logs increment in time.
Aug 1 08:16:51 blackbox kernel: BIOS-e820: 000000003eff3000 - 000000003f000000 (ACPI data)
Aug 1 08:16:52 blackbox kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Aug 1 08:16:52 blackbox kernel: 111MB HIGHMEM available.
Anyone else seen this odd behaviour?
Update: Performed a yum update and now a new kernel is available with a removal of the bodgy one sounds like someone released a bad package.