The timestamps in the database do not seem to correlate to the system clock

[mchehab]

The timestamps in the database do not seem to correlate to the system clock

[mchehab]

Whenever possible, rasdaemon tries to use the timestamps which comes from the Kernel. This way, they should match the same timestamps as shown at the dmesg.

The logic which tries to ensure that is inside select_tracing_timestamp() function: if supported by the Linux Kernel (Kernel version 3.10 and upper), it sets the tracing events to use the uptime clock.

Then, it estimates the difference from it with the one reported on userspace, and uses it internally.

As MCE won't be doing it, I would expect some differences.

Is there a way to correlate the timestamp with the clock?

Right now, no, but it should be possible to add a printk or an event tthat would store this difference at the Rasdaemon database.