From: Mark Lord <lkml@rtr.ca>
To: unlisted-recipients:; (no To-header on input)
Cc: Dave Jones <davej@redhat.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 17:17:54 -0400 [thread overview]
Message-ID: <44DCF402.4090509@rtr.ca> (raw)
In-Reply-To: <44DCF360.7050305@rtr.ca>
Mark Lord wrote:
> Mmm.. spoke too soon.
>
> I have not actually rebooted since killing powernowd,
> and it just happened again now. No powernowd running.
>
> Limit dropped from 1100Mhz to 800Mhz (log below).
Again.. with the log..
[ 3608.828000] cpufreq-core: updating policy for CPU 0
[ 3608.828000] cpufreq-core: Warning: CPU frequency out of sync: cpufreq and timing core thinks of 1100000, is 800000 kHz.
[ 3608.828000] cpufreq-core: notification 0 of frequency transition to 800000 kHz
[ 3608.828000] userspace: saving cpu_cur_freq of cpu 0 to be 800000 kHz
[ 3608.828000] cpufreq-core: notification 1 of frequency transition to 800000 kHz
[ 3608.828000] cpufreq-core: scaling loops_per_jiffy to 3195840 for frequency 800000 kHz
[ 3608.828000] userspace: saving cpu_cur_freq of cpu 0 to be 800000 kHz
[ 3608.828000] cpufreq-core: setting new policy for CPU 0: 600000 - 1100000 kHz
[ 3608.828000] freq-table: request for verification of policy (600000 - 1100000 kHz) for cpu 0
[ 3608.828000] freq-table: verification lead to (600000 - 1100000 kHz) for cpu 0
[ 3608.828000] freq-table: request for verification of policy (600000 - 800000 kHz) for cpu 0
[ 3608.828000] freq-table: verification lead to (600000 - 800000 kHz) for cpu 0
[ 3608.828000] cpufreq-core: new min and max freqs are 600000 - 800000 kHz
[ 3608.828000] cpufreq-core: governor: change or update limits
[ 3608.828000] cpufreq-core: __cpufreq_governor for CPU 0, event 3
next prev parent reply other threads:[~2006-08-11 21:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 19:55 cpufreq stops working after a while Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39 ` Mark Lord
2006-08-11 21:01 ` Dave Jones
2006-08-11 21:09 ` Mark Lord
2006-08-11 21:15 ` Mark Lord
2006-08-11 21:17 ` Mark Lord [this message]
2006-08-11 21:25 ` Mark Lord
2006-08-18 15:11 ` Pavel Machek
2006-08-24 14:44 ` Mark Lord
2006-08-24 16:15 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:18 Pallipadi, Venkatesh
2006-08-11 21:38 Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 18:25 Mark Lord
2006-08-11 18:39 ` Dave Jones
2006-08-11 19:41 ` Mark Lord
2006-08-11 20:01 ` Mark Lord
2006-08-11 20:12 ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01 ` Mark Lord
2006-08-11 19:10 ` Mark Lord
2006-08-11 19:18 ` Andrew Morton
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=44DCF402.4090509@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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