From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
To: johnstul@us.ibm.com (john stultz)
Cc: jwoithe@physics.adelaide.edu.au (Jonathan Woithe),
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rt21: slow-running clock
Date: Wed, 7 Dec 2005 14:55:46 +1030 (CST) [thread overview]
Message-ID: <200512070425.jB74Pkhq009503@auster.physics.adelaide.edu.au> (raw)
In-Reply-To: <1133928070.10613.19.camel@cog.beaverton.ibm.com> from "john stultz" at Dec 06, 2005 08:01:10 PM
> > > > When running Ingo's 2.6.14-rt21 (and in fact rt kernels back to at least
> > > > 2.6.13-rc days), the clock on my i915-based laptop runs slow. The degree
> > > > of slowness appears directly related to how busy the machine is. If
> > > > it is just sitting around doing very little the time is kept rather
> > > > well. However, as soon as the load increases the RTC and system time
> > > > diverge significantly. For example, running jackd for 2 minutes results
> > > > in the system time loosing as much as 20 seconds compared to the CMOS RTC.
> > > > Processes doing HDD I/O also seem to affect the system time similarly.
> > > >
> > > > Selectively disabling different timer-related kernel options does not make
> > > > any difference. However, the clock seems fine under vanilla 2.6.14,
> > > > suggesting an issue somewhere in the rt patches.
> > >
> > > Could you please send me your dmesg and the output of:
> > >
> > > cat /sys/devices/system/clocksource/clocksource0/*
> >
> > First the contents of the above /sys/ files:
> >
> > /sys/devices/system/clocksource/clocksource0/current_clocksource:
> > c3tsc
> >
> > /sys/devices/system/clocksource/clocksource0/available_clocksource
> > acpi_pm jiffies c3tsc pit
>
> Odd. I'm not sure why the acpi_pm wasn't chosen by default if it was
> available and the TSC fell back to the c3tsc. It might be something in
> the -RT tree that's changed that bit. Could you try the following and
> see if it doesn't resolve the timekeeping problems you're seeing?
>
> echo "acpi_pm" > /sys/devices/system/clocksource/clocksource0/current_clocksource
Will test it tonight.
> Still it sounds like something isn't right w/ either the c3tsc code or
> the cpufreq notification code. Would you be willing to test further
> patches?
Yes, no problem.
> Also could you try booting w/ idle=poll and see if that changes the
> behavior?
Again, it will be done tonight and I'll advise tomorrow.
Regards
jonathan
next prev parent reply other threads:[~2005-12-07 4:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 6:26 Jonathan Woithe
2005-12-05 19:42 ` john stultz
2005-12-07 3:39 ` Jonathan Woithe
2005-12-07 4:01 ` john stultz
2005-12-07 4:25 ` Jonathan Woithe [this message]
2005-12-07 22:54 ` Jonathan Woithe
2005-12-08 2:45 ` john stultz
2005-12-08 3:02 ` Jonathan Woithe
2005-12-08 3:22 ` john stultz
2005-12-08 4:11 ` Jonathan Woithe
2005-12-09 0:19 ` Jonathan Woithe
2005-12-09 2:11 ` john stultz
2005-12-09 2:19 ` Jonathan Woithe
2005-12-13 1:56 ` john stultz
2005-12-14 1:22 ` Jonathan Woithe
2005-12-15 1:41 ` john stultz
2005-12-15 3:18 ` Jonathan Woithe
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=200512070425.jB74Pkhq009503@auster.physics.adelaide.edu.au \
--to=jwoithe@physics.adelaide.edu.au \
--cc=johnstul@us.ibm.com \
--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
all inboxes | Powered by JetHome®