I ran into an issue where kernel logs in syslog-ng would post for wildly inappropriate times -- months in the future.
I tracked it down to the source. The issue is the dmesg time jumping. Example here:
This looks to be an issue with the Linux kernel trusting the TSC clock. The problem is discussed here:
https://forums.aws.amazon.com/thread...threadID=59753
Supposedly it was already fixed in 12.04:
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/727459
I'm going to guess that the fix is broken again in 14.04. Have other people encountered this?
I tracked it down to the source. The issue is the dmesg time jumping. Example here:
Code:
[ 0.000000] Xen version: 3.4.3.amazon (preserve-AD)
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU:
[ 0.000000] pcpu-alloc:
[ 0.000000] pcpu-alloc: [0] 0
[7493812.749226] Built 1 zonelists in Node order, mobility grouping on. Total pages: 430298
[7493812.749229] Policy zone: DMA32
[7493812.749232] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0
[7493812.750892] PID hash table entries: 4096 (order: 3, 32768 bytes)
[7493812.750945] Checking aperture...
[7493812.760330] No AGP bridge foundhttps://forums.aws.amazon.com/thread...threadID=59753
Supposedly it was already fixed in 12.04:
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/727459
I'm going to guess that the fix is broken again in 14.04. Have other people encountered this?