All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: linux-acpi@vger.kernel.org
Subject: No c2-c7 states on core i7
Date: Fri, 20 Nov 2009 15:28:56 +0100	[thread overview]
Message-ID: <4B06A7A8.109@slagter.name> (raw)

Hi there,

I already put on my flame retardant underwear, I know this is a FAQ, but 
I really need a bit of a jumpstart, google won't tell me where to start, 
so please be gentle ;-)

I bought a Gigabyte EX58-UD3R motherboard recently and put a core i7 920 
on it. This seems to be a fairly common combination.

In short: I know the core i7 does implement several C-states, from 
memory c1, c1e, c3, c6 and c7. Linux (vanilla, 2.6.31.6) does not 
recognise any of them.

The kernel configuration is very similar to the one I am running on my 
laptop with a recent mobile core2duo processor, and this one reports 
C1,C2,C3 (although it should also report yet another C state, but I 
guess that one is disabled by the bios or something alike).

Is this normal (WIP?)?

If not, where should I start debugging? I know there is "something" with 
decoding the DSDT table, but what should I look for?

I seem to remember that with an earlier linux version (before 2.6.30.5) 
it actually did work, but I am not completely sure.

Thanks for your help in advance!

Additional info that might be useful:

- all options related to power saving and C-states are ENABLED in the BIOS
- all options related to power management and idling are ENABLED in the 
kernel, which runs in 64 bits mode
- frequency switching runs fine using acpi-cpufreq and ondemand governor

If I compare the dmesg from both computers after booting, the laptop 
says "ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])" at some point, 
this message is not output at all by the server.

Output from proc/acpi/processor/CPU0/info
processor id:            0
acpi id:                 0
bus mastering control:   yes
power management:        no
throttling control:      yes
limit interface:         yes

Output from proc/acpi/processor/CPU0/power
active state:            C0
max_cstate:              C8
maximum allowed latency: 2000000000 usec
states:
     C1:                  type[C1] promotion[--] demotion[--] 
latency[000] usage[00000000] duration[00000000000000000000]


             reply	other threads:[~2009-11-20 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 14:28 Erik Slagter [this message]
2009-11-21 17:45 ` No c2-c7 states on core i7 Erik Slagter
2009-11-22 11:46 ` c1/c1e/c3/c6/c7 on linux Erik Slagter
2009-11-23  3:05 ` No c2-c7 states on core i7 ykzhao
2009-11-23  8:52   ` Erik Slagter
2009-11-23 16:11     ` Len Brown
2009-11-23 19:23       ` Erik Slagter
2009-11-23 19:26       ` Erik Slagter
2009-11-24 13:34         ` Jindrich Makovicka
2009-11-24 13:55           ` Erik Slagter
2009-11-25  6:59             ` Len Brown

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=4B06A7A8.109@slagter.name \
    --to=erik@slagter.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.