Re: [PATCH 2/2] printk, allow different timestamps for printk.time

2016-04-22 Thread Andrew Morton
On Fri, 22 Apr 2016 08:03:09 -0400 Prarit Bhargava wrote: > Over the past years I've seen many reports of bugs that include > time-stamped kernel logs (enabled when CONFIG_PRINTK_TIME=y or > print.time=1 is specified as a kernel parameter) that do not align > with either

Re: [PATCH 2/2] printk, allow different timestamps for printk.time

2016-04-22 Thread Andrew Morton
On Fri, 22 Apr 2016 08:03:09 -0400 Prarit Bhargava wrote: > Over the past years I've seen many reports of bugs that include > time-stamped kernel logs (enabled when CONFIG_PRINTK_TIME=y or > print.time=1 is specified as a kernel parameter) that do not align > with either external time stamped

[PATCH 2/2] printk, allow different timestamps for printk.time

2016-04-22 Thread Prarit Bhargava
Over the past years I've seen many reports of bugs that include time-stamped kernel logs (enabled when CONFIG_PRINTK_TIME=y or print.time=1 is specified as a kernel parameter) that do not align with either external time stamped logs or /var/log/messages. This also makes determining the time of a

[PATCH 2/2] printk, allow different timestamps for printk.time

2016-04-22 Thread Prarit Bhargava
Over the past years I've seen many reports of bugs that include time-stamped kernel logs (enabled when CONFIG_PRINTK_TIME=y or print.time=1 is specified as a kernel parameter) that do not align with either external time stamped logs or /var/log/messages. This also makes determining the time of a