From: Fred Labrosse <ffl-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Never in C3
Date: Mon, 14 Jun 2004 14:06:30 +0100 [thread overview]
Message-ID: <16589.41686.480893.225338@aber.ac.uk> (raw)
All,
The following seems to suggest that my processor is never in C3 state:
# cat /proc/acpi/processor/CPU0/power
active state: C1
default state: C1
bus master activity: db66ffff
states:
*C1: promotion[C2] demotion[--] latency[000] usage[02058670]
C2: promotion[C3] demotion[C1] latency[020] usage[19743630]
C3: promotion[--] demotion[C2] latency[200] usage[00000000]
Right?
I did read at some point that this was because of hotplug. I thus stopped
hotplug and, at that time, I did see my processor in C3 state. Hoever,
since then, I've never seen that again, and hotplug is not running.
And yes, C3 is claimed to be supported (from dmesg:
ACPI: Processor [CPU0] (supports C1 C2 C3, 8 throttling states)
)
Anything else that could cause that? Any hints?
Cheers,
Fred
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next reply other threads:[~2004-06-14 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 13:06 Fred Labrosse [this message]
[not found] ` <16589.41686.480893.225338-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2004-06-14 14:33 ` Never in C3 Karol Kozimor
[not found] ` <20040614143312.GA16952-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-06-15 13:35 ` Fred Labrosse
[not found] ` <16590.64317.405885.159934-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2004-06-15 15:32 ` Karol Kozimor
2004-06-15 17:39 ` Matthew Garrett
[not found] ` <1087321154.10618.0.camel-myFlNLNQP+Q@public.gmane.org>
2004-06-15 19:03 ` Nate Lawson
2004-06-16 11:36 ` Frank Mehnert
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=16589.41686.480893.225338@aber.ac.uk \
--to=ffl-4cldhec3iye1qrn1bg8bzw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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