From: Thomas Renninger <trenn@suse.de>
To: Michael Reinelt <michael@reinelt.co.at>
Cc: Dave Jones <davej@redhat.com>, cpufreq@lists.linux.org.uk
Subject: Re: Core2Duo locked at 800MHz
Date: Tue, 27 Nov 2007 11:47:28 +0100 [thread overview]
Message-ID: <1196160448.23251.21.camel@queen.suse.de> (raw)
In-Reply-To: <474BB4F2.9040604@reinelt.co.at>
On Tue, 2007-11-27 at 06:10 +0000, Michael Reinelt wrote:
> Hi Dave,
>
> thanks for your answer!
>
> > > When I boot the notebook into single-user mode
> > > (using vanilla 2.6.23 or 2.6.24-rc3), with no modules loaded, the cpu
> > > runs at 2.4GHz. As soon as I laod the acpi-cpufreq module, the upper
> > > limit falls in some steps (2 GHz, 1200MHz) to 800 MHz. Note that there
> > > is neither acpid nor any powersave daemon running!
> >
> > Do you have CONFIG_CPU_FREQ_GOV_ONDEMAND enabled in your kernel ?
>
> Yes, but as a module.
>
> > > At the moment my workaround is *not* to load acpi-cpufreq, so the CPU
> > > stays at 2.4GHz all the time, but I really want to use powersaving with
> > > the machine....
> >
> > I'm confused. It sounds like you _are_ using power saving.
> > The whole purpose of cpufreq is to lower the cpu speed when idle.
> I _want_ to use powersaving, but I can't, because I'd be stuck at 800 MHz.
>
> > If you run some cpu intensive load like a big compile, does the
> > speed go back up ?
> No, it does not.
>
> > the cpufreq.debug=7 logs would be a good start.
It is probably limited through _PPC again.
Dave, Len: Can you please add the patch that _PPC changes are printed
with cpufreq.debug, pls.
I posted this a while ago on the cpufreq list:
Subject: [PATCH] Print _PPC changes via cpufreq debug layer
http://article.gmane.org/gmane.linux.kernel.cpufreq/5642
Thanks,
Thomas
next prev parent reply other threads:[~2007-11-27 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 6:49 Core2Duo locked at 800MHz Michael Reinelt
2007-11-26 19:09 ` Dave Jones
2007-11-27 6:10 ` Michael Reinelt
2007-11-27 10:47 ` Thomas Renninger [this message]
2007-11-27 14:36 ` Michael Reinelt
2007-11-27 14:53 ` Thomas Renninger
2007-11-27 15:27 ` Pallipadi, Venkatesh
2007-11-27 19:05 ` Dave Jones
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=1196160448.23251.21.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=michael@reinelt.co.at \
/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