mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "john stultz" <johnstul@us.ibm.com>
To: "Martin Knoblauch" <spamtrap@knobisoft.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)
Date: Wed, 7 May 2008 10:07:49 -0700	[thread overview]
Message-ID: <1f1b08da0805071007t37d7db7fn40daaf2d17fba0f1@mail.gmail.com> (raw)
In-Reply-To: <177578.8968.qm@web32608.mail.mud.yahoo.com>

On Wed, May 7, 2008 at 5:42 AM, Martin Knoblauch <spamtrap@knobisoft.de> wrote:
> Hi,
>
>   any news on the one below? I upgraded to 2.6.25.2 and the problem still persists. Would adding a bugzilla actually help ? :-)
>
>
>  http://www.ussg.iu.edu/hypermail/linux/kernel/0804.2/1144.html

With this issue you're seeing is only the printk timestamps jumping
back, correct?

For example, you're not seeing the output from gettimeofday() or the
actual jiffies value (as seen from maybe a driver) jump backward? Is
that right?

The printk timestamps may jump around a bit at bootup,  especially if
you have unsynced TSCs, so that is a known issue. However its not
known to have any actual negative effect other then maybe causing the
dmesg log to be a bit confusing.

thanks
-john

  parent reply	other threads:[~2008-05-07 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 12:42 Martin Knoblauch
2008-05-07 12:56 ` Henrique de Moraes Holschuh
2008-05-07 13:06 ` Bart Van Assche
2008-05-07 17:07 ` john stultz [this message]
2008-05-07 15:02 Martin Knoblauch
2008-05-07 15:50 Martin Knoblauch
2008-05-08 10:29 ` Thomas Gleixner
2008-05-08 12:21   ` Gabriel C
2008-05-07 18:14 Martin Knoblauch
2008-05-07 18:59 ` John Stultz
2008-05-08 14:05 Martin Knoblauch
2008-05-08 14:13 ` Thomas Gleixner
2008-05-08 17:31   ` Mike Galbraith
2008-05-08 16:41 Martin Knoblauch
2008-05-09 11:06 Martin Knoblauch
2008-05-09 11:32 Martin Knoblauch
2008-05-09 13:01 Martin Knoblauch
2008-05-09 15:18 Martin Knoblauch

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=1f1b08da0805071007t37d7db7fn40daaf2d17fba0f1@mail.gmail.com \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spamtrap@knobisoft.de \
    /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
Powered by JetHome