mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Martin Knoblauch <spamtrap@knobisoft.de>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
	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: Thu, 8 May 2008 12:29:52 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805081227250.3318@apollo.tec.linutronix.de> (raw)
In-Reply-To: <530038.77501.qm@web32608.mail.mud.yahoo.com>

On Wed, 7 May 2008, Martin Knoblauch wrote:
> > 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
> 
>  interesting - maybe related to clocksources. The HPET seems to be detected later in 2.6.25:
> 
> 2.6.24:
> 
> [    0.000000] Initializing CPU#0
> [    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
> -->[    0.000000] hpet clockevent registered
> -->[    0.000000] TSC calibrated against HPET
 
> 2.6.25.2:
> 
> [    0.000000] Initializing CPU#0
> [    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
> -->[    0.000000] TSC calibrated against PM_TIMER
 
That's odd indeed. Is HPET not registered at all in 2.6.25 or does it just happen late ?

please provide the output of:
/sys/devices/system/clocksource/clocksource0/available_clocksource
/sys/devices/system/clocksource/clocksource0/current_clocksource

Thanks,
	tglx

  reply	other threads:[~2008-05-08 10:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 15:50 Martin Knoblauch
2008-05-08 10:29 ` Thomas Gleixner [this message]
2008-05-08 12:21   ` Gabriel C
  -- strict thread matches above, loose matches on Subject: below --
2008-05-09 15:18 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:02 Martin Knoblauch
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=alpine.LFD.1.10.0805081227250.3318@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bart.vanassche@gmail.com \
    --cc=hmh@hmh.eng.br \
    --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

all inboxes | Powered by JetHome®