Knut Petersen <[email protected]> wrote:
>
> Obviously printk time jumps. But it is also inaccurate compared against
> system time: 10:33:18 is
> 1116 seconds after 10:14:42, and so the printk time at 10:33:18 should
> be 1260+1116==2376 and not 2362.
> That means printk time lost 14 seconds against system time in less that
> 20 Minutes.
printk-time is really just a debugging/development thing - it doesn't try
to be serious.
We _could_ use some more accurate time function for this, but most of them
take locks, and taking locks inside printk isn't a great idea.
Plus syslogd already adds timestamps.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
