From: Stephen Clark <Stephen.Clark@seclark.us>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpuinfo_cur_freq always max
Date: Tue, 18 Dec 2007 16:39:42 -0500 [thread overview]
Message-ID: <47683E1E.4010001@seclark.us> (raw)
In-Reply-To: <x71w9k6lbf.fsf@saeurebad.de>
Johannes Weiner wrote:
>Hi,
>
>Stephen Clark <Stephen.Clark@seclark.us> writes:
>
>
>
>>userspace
>>
>>
>
>Please supply the full dmesg output on the non-working kernel the
>corresponding .config (or /proc/config.gz).
>
>Added Dave to CC.
>
> Hannes
>
>
>
Duh - I rebooted into the new kernel and no longer see the behavior I
described above. Maybe I had something going in
the background i didn't realize. Thing was I even started a bash empty
while loop to see if /proc/cpuinfo speed would go
up and it did.
I have an applet that displays on my kde kicker panel that every 2
seconds reads /sys/.../cpuinfo_cur_freq and it was
sitting on the max speed all the time. Hmmm.
Well Thanks for the response and sorry for the false alarm.
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)
prev parent reply other threads:[~2007-12-18 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:51 cpuinfo_cur_freq always max Stephen Clark
2007-12-17 21:27 ` 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 [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=47683E1E.4010001@seclark.us \
--to=stephen.clark@seclark.us \
--cc=davej@codemonkey.org.uk \
--cc=hannes@saeurebad.de \
--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