diff options
| author | Julius Werner <jwerner@chromium.org> | 2017-04-12 13:24:23 -0700 |
|---|---|---|
| committer | Julius Werner <jwerner@chromium.org> | 2017-04-19 00:38:19 +0200 |
| commit | 4d9fafa3a9be3574945f26e58cd96a1720386197 (patch) | |
| tree | 464ed8941c4f55dfe24fe2c03f6bda77723f557f | |
| parent | e0f30920f091869562627f7c9d22635c3fa8f2fb (diff) | |
| download | coreboot-4d9fafa3a9be3574945f26e58cd96a1720386197.tar.xz | |
elog: Print timestamp when logging event
We're already reading the RTC whenever we file an event, we might as
well print out the value at that time. Having a few RTC timestamps in
the firmware log makes it easier to correlate that part of the log to a
particular boot once we start having multiple boots in the log.
Change-Id: I750dd18aa2c43c95b8c1fbb8f404c1e3a77bec73
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/19305
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
| -rw-r--r-- | src/drivers/elog/elog.c | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/src/drivers/elog/elog.c b/src/drivers/elog/elog.c index 0f72e7cf6c..27b6e2970d 100644 --- a/src/drivers/elog/elog.c +++ b/src/drivers/elog/elog.c @@ -881,8 +881,15 @@ int elog_add_event_raw(u8 event_type, void *data, u8 data_size) elog_mirror_increment_last_write(event_size); - printk(BIOS_INFO, "ELOG: Event(%X) added with size %d\n", + printk(BIOS_INFO, "ELOG: Event(%X) added with size %d ", event_type, event_size); + if (event->day != 0) { + printk(BIOS_INFO, "at 20%02x-%02x-%02x %02x:%02x:%02x UTC\n", + event->year, event->month, event->day, + event->hour, event->minute, event->second); + } else { + printk(BIOS_INFO, "(timestamp unavailable)\n"); + } /* Shrink the log if we are getting too full */ if (elog_shrink() < 0) |