Be careful what you ask for.
This is _not_ a true (time-of-day) timestamp. At least it wasn't last I
looked. Think kernel active time since boot - useful for relative (timed)
occurrences for kernel events.
It would be reasonably trivial to adjust it to a ToD stamp, but it's going to
have some holes
On Fri, 20 Apr 2012, Aria Bamdad wrote:
by default on s390x. I also found some stuff online hinting that it is off
on Red Hat also.
Not just a hint -- the Red Hat kernel configuration appears
not to enable it -- but it may be trivially turned on:
# echo 1 > /sys/module/printk/parameters/pri
.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Christian Paro
Sent: Friday, April 20, 2012 5:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Kernel ring buffer date stams missing
Of course, if you don't need the time stamps for early boot, you can
Of course, if you don't need the time stamps for early boot, you can turn
them on at runtime through the /sys filesystem:
http://elinux.org/Debugging_by_printing#Printk_Timestamps
On Fri, Apr 20, 2012 at 4:57 PM, Christian Paro wrote:
> Just a guess here, but maybe the s390x kernel for SLES 11 S
Just a guess here, but maybe the s390x kernel for SLES 11 SP1 was compiled
with CONFIG_PRINTK_TIME disabled, while the x86-64 kernel had the same
option enabled?
I do see those time-offset numbers at the beginning of output from other
kernels on s390x, so I don't think it's a difference inherent t
Hi,
Anyone knows why the kernel ring buffer (dmesg) is missing the usual time
stamp prefix on each line on System z? For example:
SUSE SLES 11 SP1 on system z shows this:
Write protected kernel read-only data: 0x10 - 0x5f
While Intel (same OS) shows:
[1.611026] Write pro
