cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jwilson@redhat.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: cpufreq@lists.linux.org.uk, "Frazier, John" <j-frazier2@ti.com>
Subject: Re: cpufreq question
Date: Wed, 14 May 2008 15:22:45 -0400	[thread overview]
Message-ID: <200805141522.46055.jwilson@redhat.com> (raw)
In-Reply-To: <6453C3CB8E2B3646B0D020C112613273093959@sausexmb4.amd.com>

On Wednesday 14 May 2008 02:52:37 pm Langsdorf, Mark wrote:
> > On Wednesday 14 May 2008 02:28:02 pm Frazier, John wrote:
> > > I am new to Linux and I am having a little problem with my cpu power
> > > saving.
> > >
> > > Kernel: 2.6.9-67.0.4.ELsmp
> > >
> > > I am using cpuspeed to control my cpus and I have just upgraded to a
> > > newer version of it and it is looking for the file
> > > /sys/devices/system/cpu/cpu%u/cpufreq/affected_cpus.
> > >
> > > This file does not exist on my system. What is the correct way to
> > > resolve this issue?
> >
> > Probably best to file a bug at bugzilla.redhat.com for issues
> > on a RHEL4 system -- wildly divergent from upstream by now.
>
> RHEL4 doesn't support
> /sys/devices/system/cpu/cpu%u/cpufreq/affected_cpus and
> cpuspeed 1.2.1 requires them.  You need to revert to a
> previous version of cpuspeed, such as the one that came
> with your RHEL4 installation.  Current versions of RHEL4
> support SMP/CMP cpufreq with their native tools.

Erm, RHEL4 has been shipping cpuspeed 1.2.1 since mid 2005... From the 
kernel-utils changelog:

* Mon Jun 20 2005 Dave Jones <davej@redhat.com>
- Update cpuspeed to 1.2.1, featuring improved dual-core/SMP support. 
(#146179)


-- 
Jarod Wilson
jwilson@redhat.com

  parent reply	other threads:[~2008-05-14 19:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 18:28 cpufreq question Frazier, John
2008-05-14 18:44 ` Jarod Wilson
2008-05-14 18:52   ` Langsdorf, Mark
2008-05-14 19:11     ` Frazier, John
2008-05-14 19:19       ` Langsdorf, Mark
2008-05-14 19:31         ` Frazier, John
2008-05-14 20:47           ` Pallipadi, Venkatesh
2008-05-14 20:54             ` Jarod Wilson
2008-05-16 21:58           ` Carl Thompson
2008-05-16 22:01           ` Carl Thompson
2008-05-16 22:03           ` Carl Thompson
2008-05-16 22:05           ` Carl Thompson
2008-05-14 19:27       ` Jarod Wilson
2008-05-14 19:22     ` Jarod Wilson [this message]
2008-05-14 19:25       ` Langsdorf, Mark
2008-05-14 19:43         ` Jarod Wilson

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=200805141522.46055.jwilson@redhat.com \
    --to=jwilson@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=j-frazier2@ti.com \
    --cc=mark.langsdorf@amd.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