On 2011-04-19 06:24, Julien BLACHE wrote:
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.
It's certainly not expected, but where would it be documented?
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.
...so why isn't mcelog using that time?
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.
OK but note that I'm not talking about the time in the log, but the time
outputted when running mcelog.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
