From: Stephen Clark <Stephen.Clark@seclark.us>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: cpuinfo_cur_freq always max
Date: Mon, 17 Dec 2007 12:51:32 -0500 [thread overview]
Message-ID: <4766B724.7090106@seclark.us> (raw)
Hello,
Running linux 2.6.23.1-21.fc7
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
correctly reflects the cpu speed, when idle it is 996000 and when
compiling it is 1826000.
Its also the same as what is in /proc/cpuinfo.
But with 2.6.23.8-34.fc7
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
is always the max cpu speed of 1826000.
While cpuinfo_cur_freq is the max 1826000 /proc/cpuinfo relflects the
correct speed when idle of
996000
This is on an asus laptop with an intel core 2 duo T5600 processor.
Anyone else see this problem.
Regards,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next reply other threads:[~2007-12-17 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:51 Stephen Clark [this message]
2007-12-17 21:27 ` cpuinfo_cur_freq always max Johannes Weiner
[not found] ` <4766ECDB.1040203@seclark.us>
2007-12-17 22:09 ` Johannes Weiner
2007-12-18 15:19 ` Stephen Clark
2007-12-18 16:04 ` Johannes Weiner
2007-12-18 21:39 ` Stephen Clark
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=4766B724.7090106@seclark.us \
--to=stephen.clark@seclark.us \
--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 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.