From: Wolfgang Hoffmann <woho@woho.de>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Lee Revell <rlrevell@joe-job.com>
Subject: Re: [-rt] time-related problems with CPU frequency scaling
Date: Thu, 20 Apr 2006 20:39:30 +0200 [thread overview]
Message-ID: <200604202039.31008.woho@woho.de> (raw)
In-Reply-To: <200604162041.10844.woho@woho.de>
On Sunday 16 April 2006 20:41, Wolfgang Hoffmann wrote:
> Now with speedstep enabled and CONFIG_HIGH_RES_TIMERS=y, I see some
> anomalies:
> - time-of-day lags gradually behind wallclock time
It turns out that this is a non-issue. I can't quite explain how I came to the
impression that there is a clock lag, but current status is that the clock
runs correctly. So sorry for the noise.
On Tuesday 18 April 2006 00:35, Lee Revell wrote:
> On Sun, 2006-04-16 at 20:41 +0200, Wolfgang Hoffmann wrote:
> > - if CPU frequency is low when jackd is started, it complains:
> > "delay of 2915.000 usecs exceeds estimated spare
> > time of 2847.000; restart ..."
> > as soon as frequency is scaled up. Seems that jackd gets confused by
> > some influence of CPU frequency on timekeeping? No problems as long as
> > CPU frequency isn't scaled up, though.
>
> JACK still uses the TSC for timing and thus is incompatible with CPU
> frequency scaling. You must use the -clockfix branch from CVS.
Thanks for the pointer, Lee. I'm now running the clockfix CVS branch and the
problems are solved. So the -rt kernel is fine.
Thanks for the help,
Wolfgang
prev parent reply other threads:[~2006-04-20 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 18:41 [-rt] time-related problems with CPU frequency scaling Wolfgang Hoffmann
2006-04-17 22:35 ` Lee Revell
2006-04-18 6:11 ` Wolfgang Hoffmann
2006-04-18 6:32 ` Lee Revell
2006-04-20 18:39 ` Wolfgang Hoffmann [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=200604202039.31008.woho@woho.de \
--to=woho@woho.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.