From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Core i7 M620 power management problem
Date: Wed, 29 Dec 2010 11:40:54 -0600 [thread overview]
Message-ID: <AANLkTi=RHwZeyjuBpPuTBfz2-uk2qTZPNJ7SmeEECwZB@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinXG9CQmAOp4x=_ybTUu2+0Z8==wR=yDNJGDqVE@mail.gmail.com>
On Wed, Dec 29, 2010 at 11:13 AM, Bill Longman <bill.longman@gmail.com> wrote:
> A strangeness I have noted is that /proc/cpuinfo has this for its power
> capabilities:
> power management:
> Nothing.
FWIW I have Core i7 920, and it also has nothing in the power
management in cpuinfo, but CPU frequency scaling does work and speeds
change (using ondemand governor, in a desktop machine).
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_*
2661000 2660000 2527000 2394000 2261000 2128000 1995000 1862000 1729000 1596000
conservative userspace powersave ondemand performance
1596000
acpi-cpufreq
ondemand
2661000
1596000
<unsupported>
So it seems similar to yours except that your max_freq and min_freq
are the same! Which matches what you say about it never going faster
than the minimum speed.
In kernel docs Documentation/cpu-freq/cpu-drivers.txt there is some
information about how the min and max speed are set by the policy that
is in use (by whatever driver is controlling the scaling). So I don't
know if there is a userspace program (like KDE laptop stuff) that
might be overriding with its own faulty settings?
Seems like your kernel settings are probably okay since you can see
all of that so far. If you run powertop can it see all of the C-states
and P-states without any problems?
next prev parent reply other threads:[~2010-12-29 17:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 17:13 [gentoo-user] Core i7 M620 power management problem Bill Longman
2010-12-29 17:40 ` Paul Hartman [this message]
2010-12-29 18:35 ` Stefan G. Weichinger
2010-12-29 18:48 ` Bill Longman
2010-12-29 19:55 ` Stefan G. Weichinger
[not found] ` <AANLkTik3UmVwYwejLmV=trDN+W7443eY4yQRfn3=_m4e@mail.gmail.com>
2010-12-29 20:51 ` Bill Longman
2010-12-30 0:22 ` Paul Hartman
2010-12-30 2:56 ` Bill Longman
2010-12-30 7:59 ` Mick
2010-12-30 16:45 ` Bill Longman
2010-12-30 17:55 ` Mick
2010-12-30 18:13 ` Bill Longman
2010-12-30 0:43 ` Mick
2010-12-30 3:16 ` Bill Longman
2010-12-30 8:21 ` Mick
2010-12-30 17:10 ` Bill Longman
2010-12-30 8:59 ` Stefan G. Weichinger
2010-12-30 16:25 ` Bill Longman
2010-12-30 17:54 ` Bill Longman
2010-12-30 22:44 ` Stefan G. Weichinger
2010-12-31 1:22 ` Bill Longman
2010-12-31 10:59 ` Mick
2011-01-01 11:16 ` Stefan G. Weichinger
2011-01-01 20:10 ` Bill Longman
2011-01-01 23:50 ` Bill Longman
2011-01-02 0:34 ` Mick
2011-01-02 4:39 ` Bill Longman
2011-01-02 11:59 ` Mick
2010-12-30 3:51 ` Bill Longman
2010-12-29 19:57 ` Stefan G. Weichinger
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='AANLkTi=RHwZeyjuBpPuTBfz2-uk2qTZPNJ7SmeEECwZB@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.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