linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: Dave Jones <davej@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [BUG] jiffies counter leaps in 2.6.24-rc3
Date: Thu, 29 Nov 2007 18:57:43 +0100	[thread overview]
Message-ID: <20071129185743.46daa8ad@morte> (raw)
In-Reply-To: <20071129174548.GC12481@redhat.com>

On Thu, 29 Nov 2007 12:45:48 -0500
Dave Jones <davej@redhat.com> wrote:

> Hmm, what's
> in /sys/devices/system/clocksource/clocksource0/current_clocksource  ?

morte st3 # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
acpi_pm
 
> adjust_jiffies() always gets called on a speed transition. I'm wondering
> if perhaps we shouldn't do that if we're using something other than
> the tsc for timekeeping.

I gave other clocksources a try:

morte st3 # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm pit jiffies tsc

Setting tsc as current clocksource:
morte st3 # echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
[13367.729060] Time: tsc clocksource has been installed.
didn't fix anything. Other weirdness here: it looks like it affects my
typematic delay and repeat rate.

Setting jiffies or pit as current clocksource didn't fix anything, but at
least it doesn't cause anything bad.

Do you want me to comment out adjust_jiffies() and see what happens?


-- 
Ciao
Stefano

  reply	other threads:[~2007-11-29 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 16:51 [BUG] jiffies counter leaps in 2.6.24-rc3 Stefano Brivio
2007-11-24 17:56 ` Frans Pop
2007-11-24 18:09   ` Stefano Brivio
2007-11-24 18:48 ` Rafael J. Wysocki
2007-11-24 18:46   ` Stefano Brivio
2007-11-24 19:31     ` Rafael J. Wysocki
2007-11-26 18:00       ` Stefano Brivio
2007-11-29  7:20       ` Stefano Brivio
2007-11-29 10:33         ` Ingo Molnar
2007-11-29  8:50       ` Stefano Brivio
2007-11-29 10:35         ` Ingo Molnar
2007-11-29 17:45           ` Dave Jones
2007-11-29 17:57             ` Stefano Brivio [this message]
2007-11-29 18:24               ` Dave Jones
2007-11-29 19:25                 ` Stefano Brivio
2007-11-29 19:36                   ` Ingo Molnar
2007-11-29 20:12                     ` Stefano Brivio
2007-11-29 20:04                   ` Dave Jones

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=20071129185743.46daa8ad@morte \
    --to=stefano.brivio@polimi.it \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).