notfound 623266 1.0~pre3-3
close 623266
thanks

Filipus Klutiero <chea...@gmail.com> wrote:

Hi,

> TIME 1303155852 Mon Apr 18 15:44:12 2011 is when I ran mcelog, rather
> than when each error occured. I have seen this issue every time mcelog
> outputted errors.

This is the expected and documented behaviour. MCE events don't come
with wall time attached to them, the best you can have is the time the
kernel collected them from the CPU.

mcelog runs as a daemon (by default) or trigger (user configurable)
these days, so the time you get in the log is the time the kernel
collected the event.

JB.

-- 
 Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> 
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to