public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: linux-kernel@vger.kernel.org, hmh@hmh.eng.br
Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)
Date: Wed, 7 May 2008 08:02:23 -0700 (PDT)	[thread overview]
Message-ID: <814762.71071.qm@web32606.mail.mud.yahoo.com> (raw)

----- Original Message ----

> From: Bart Van Assche <bart.vanassche@gmail.com>
> To: Martin Knoblauch <spamtrap@knobisoft.de>
> Cc: linux-kernel@vger.kernel.org; hmh@hmh.eng.br
> Sent: Wednesday, May 7, 2008 3:06:02 PM
> Subject: Re: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)
> 
> On Wed, May 7, 2008 at 2:42 PM, Martin Knoblauch wrote:
> >
> >  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
> 
> I noticed a similar issue on 2.6.22 and 2.6.24 kernels: with ACPI
> disabled Linux' clock jumps backward and forward early during boot.
> See also the kernel messages from the attachment in comment #13 of
> http://bugzilla.kernel.org/show_bug.cgi?id=9936.
> 
> Bart,

Hi Bart,

 no this looks different. As soon as the timesource is detected, I see non-zero timestamps
in dmesg, but they look smaller and jump in both directions. And I have never seen this before
2.6.25.

 It actually might be a good idea to get the dmesg output from 2.6.24.

Cheers
Martin


             reply	other threads:[~2008-05-07 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 15:02 Martin Knoblauch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-09 15:18 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24) Martin Knoblauch
2008-05-09 13:01 Martin Knoblauch
2008-05-09 11:32 Martin Knoblauch
2008-05-09 11:06 Martin Knoblauch
2008-05-08 16:41 Martin Knoblauch
2008-05-08 14:05 Martin Knoblauch
2008-05-08 14:13 ` Thomas Gleixner
2008-05-08 17:31   ` Mike Galbraith
2008-05-07 18:14 Martin Knoblauch
2008-05-07 18:59 ` John Stultz
2008-05-07 15:50 Martin Knoblauch
2008-05-08 10:29 ` Thomas Gleixner
2008-05-08 12:21   ` Gabriel C
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

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=814762.71071.qm@web32606.mail.mud.yahoo.com \
    --to=spamtrap@knobisoft.de \
    --cc=bart.vanassche@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.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