linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: youquan_song@linux.intel.com
To: linux-kernel@vger.kernel.org
Cc: youquan.song@intel.com
Subject: kernel-2.6.25-rc2, CPU C state "active state" always remain C0 unchangeable by cat  'proc/'
Date: Wed, 20 Feb 2008 23:01:19 -0800 (PST)	[thread overview]
Message-ID: <1638.172.16.116.56.1203577279.squirrel@linux.intel.com> (raw)

On Fedora9 Alpha with  kernel-2.6.25-rc2,
I run " watch -n 0.1 "cat /proc/acpi/processor/CPU*/power | grep 'active
state'" ", I find that the CPU C state information "active state" remain
at "C0" and it do not change any time. The same issue also exit on
2.6.24-rc2 kernel.
But with RHEL5.1 kernel-2.6.18 the CPU C state information is normal.


Every 0.1s: cat /proc/acpi/processor/CPU*/power | grep 'active state'     
                                                                        
Thu Feb 21 09:44:33 2008

active state:            C0
active state:            C0
active state:            C0
active state:            C0
active state:            C0
active state:            C0
active state:            C0
active state:            C0

On RHEL5.1  kernel-2.6.18-53.el5
[root@localhost ~]# cat /proc/acpi/processor/CPU*/power | grep 'active state'
active state:            C2
active state:            C2
active state:            C2
active state:            C2
active state:            C2
active state:            C3
active state:            C2
active state:            C3

The hardware platform: bensley and santarosa.


             reply	other threads:[~2008-02-21  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  7:01 youquan_song [this message]
2008-02-21 20:24 ` kernel-2.6.25-rc2, CPU C state "active state" always remain C0 unchangeable by cat 'proc/' Pallipadi, Venkatesh

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=1638.172.16.116.56.1203577279.squirrel@linux.intel.com \
    --to=youquan_song@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=youquan.song@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).