From: Andrew Morton <akpm@osdl.org>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [BUG] Timer subsystem broken for Pentium M / early XEON / P6 family
Date: Sat, 21 Jan 2006 12:47:09 -0800 [thread overview]
Message-ID: <20060121124709.28756a2d.akpm@osdl.org> (raw)
In-Reply-To: <43D22139.2000208@t-online.de>
Knut Petersen <Knut_Petersen@t-online.de> 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.
prev parent reply other threads:[~2006-01-21 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 11:55 [BUG] Timer subsystem broken for Pentium M / early XEON / P6 family Knut Petersen
2006-01-21 20:47 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060121124709.28756a2d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Knut_Petersen@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox