lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1638.172.16.116.56.1203577279.squirrel@linux.intel.com>
Date:	Wed, 20 Feb 2008 23:01:19 -0800 (PST)
From:	youquan_song@...ux.intel.com
To:	linux-kernel@...r.kernel.org
Cc:	youquan.song@...el.com
Subject: kernel-2.6.25-rc2,
      CPU C state "active state" always remain C0 unchangeable by cat 
     'proc/'

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@...alhost ~]# 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ