From: Niko Ehrenfeuchter <ehrenfeu@informatik.uni-freiburg.de>
To: linux-acpi@vger.kernel.org
Subject: Re: CPU - Power state (Cx) usage count not working
Date: Mon, 23 Jan 2006 11:40:06 +0100 [thread overview]
Message-ID: <1138012807.2948.9.camel@spitfire> (raw)
In-Reply-To: <43D491A5.6010000@sbox.tugraz.at>
Hi Gerfried,
On Mon, 2006-01-23 at 09:19 +0100, Gerfried Maier wrote:
> Hi everybody!
>
> According to the ACPI4Linux doc
>
> cat /proc/acpi/processor/CPU0/power
>
> should look like
>
> active state: C2
> default state: C1
> bus master activity: 00004f00
> states:
> C1: promotion[C2] demotion[--] latency[000]
> usage[00033670]
> *C2: promotion[C3] demotion[C1] latency[084]
> usage[00357060]
> C3: promotion[--] demotion[C2] latency[120]
> usage[00000000]
>
> Unfortunaltely on my system (P4m 1800Mhz; 2.4.31 or .32) the usage count
> shows always 00000000. Unloading several modules (eg usb-ohci) has no
> effect.
the counter normally shows the de facto usage, so I assume your system
never uses C3 in the above situation. Unloading the usb-modules on a 2.4
kernel _might_ help, but it also might not suffice. If you have anything
that causes busmaster activity, your system will never use C3. This
could be a module (as said above, the usb-modules on 2.4 do so - that's
fixed in the 2.6 series) as well as some process, e.g. sound output or
some monitoring stuff (I remember gkrellm once preventing my system to
enter C3). To check this, you could try to boot into single-user mode,
unload all unnecessary modules and then recheck for C3 usage.
Some time ago, I wrote a couple of lines considering the c-states with
kernel 2.4 on the acpi-wiki. You can have a look there:
http://acpi.sourceforge.net/wiki/index.php/WhyMyCxPowerStateIsNotUsed
hth,
Niko
next prev parent reply other threads:[~2006-01-23 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 8:19 CPU - Power state (Cx) usage count not working Gerfried Maier
2006-01-23 10:40 ` Niko Ehrenfeuchter [this message]
2006-01-23 11:39 ` Gerfried Maier
2006-01-23 12:33 ` Niko Ehrenfeuchter
2006-02-01 14:44 ` Gerfried Maier
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=1138012807.2948.9.camel@spitfire \
--to=ehrenfeu@informatik.uni-freiburg.de \
--cc=linux-acpi@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