Gentoo Archives: gentoo-user

From: Bill Longman <bill.longman@×××××.com>
To: lists@×××××.at, gentoo-user@l.g.o
Subject: Re: [gentoo-user] Core i7 M620 power management problem
Date: Wed, 29 Dec 2010 20:53:34
Message-Id: AANLkTinY14DgMBGxpFYT9=YebzfV4z1Tie1vMBF1EJg9@mail.gmail.com
1 >
2 > Yeah, the cpufreq utils show all the relevant information. I use the
3 > acpi-cpufreq driver and when I didn't use it nothing happened. cpufreq-aperf
4 > shows each CPU at 1.2GHz. I'll look at the EIST in BIOS, too. Thanks for the
5 > pointers.
6 >
7
8 Here's an interesting item:
9
10 12:41:00# cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit
11 1199000
12
13 which sort of jives with the "asserted by call to hardware" in the
14 cpufreq-info section:
15 analyzing CPU 3:
16 driver: acpi-cpufreq
17 CPUs which run at the same hardware frequency: 0 1 2 3
18 CPUs which need to have their frequency coordinated by software: 3
19 maximum transition latency: 10.0 us.
20 hardware limits: 1.20 GHz - 2.67 GHz
21 available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27
22 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz,
23 1.20 GHz
24 available cpufreq governors: conservative, ondemand, userspace, powersave,
25 performance
26 current policy: frequency should be within 1.20 GHz and 1.20 GHz.
27 The governor "performance" may decide which speed to use
28 within this range.
29 current CPU frequency is 1.20 GHz (asserted by call to hardware).
30 cpufreq stats: 2.67 GHz:0.25%, 2.67 GHz:0.01%, 2.53 GHz:0.01%, 2.40
31 GHz:0.01%, 2.27 GHz:0.01%, 2.13 GHz:0.01%, 2.00 GHz:0.01%, 1.87 GHz:0.01%,
32 1.73 GHz:0.01%, 1.60 GHz:0.01%, 1.47 GHz:0.01%, 1.33 GHz:0.01%, 1.20
33 GHz:99.61% (28)
34
35 So, why are there micro-spikes of higher frequencies in the above stats? The
36 stats section says there are only five transitions.
37
38
39 --
40 Bill Longman

Replies

Subject Author
Re: [gentoo-user] Core i7 M620 power management problem Paul Hartman <paul.hartman+gentoo@×××××.com>
Re: [gentoo-user] Core i7 M620 power management problem Mick <michaelkintzios@×××××.com>