printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock timestamp to printk messages. The local hardware clock loses time each day making it difficult to determine exactly when an issue has occurred in the kernel log, and making it difficult to determine how kernel and hardware issues relate to each other in real time.
Signed-off-by: Tudor Ambarus tudor.ambarus@linaro.org --- syzkaller-start | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/syzkaller-start b/syzkaller-start index 305d09d..8bcc23a 100644 --- a/syzkaller-start +++ b/syzkaller-start @@ -65,8 +65,9 @@ if [ "${url}" == "" ]; then usage fi
+KERNEL_PARAMS="printk.time=y " if [ -n "${GDB}" ]; then - KERNEL_PARAMS="nokaslr norandmaps" + KERNEL_PARAMS+="nokaslr norandmaps" fi
reset # Required on subsequent runs, since QEMU borks the terminal