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>
This commit is contained in:
parent
e0f30920f0
commit
4d9fafa3a9
|
@ -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)
|
||||
|
|
Loading…
Reference in New Issue