From: ykzhao <yakui.zhao@intel.com>
To: Erik Slagter <erik@slagter.name>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: No c2-c7 states on core i7
Date: Mon, 23 Nov 2009 11:05:12 +0800 [thread overview]
Message-ID: <1258945512.3773.33.camel@localhost.localdomain> (raw)
In-Reply-To: <4B06A7A8.109@slagter.name>
On Fri, 2009-11-20 at 22:28 +0800, Erik Slagter wrote:
> 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.
Will you please attach the output of acpidump on the machine with the
core i7 cpu?
Please attach the output of every file
under /sys/firmware/acpi/tables/dynamic/SSDT*?
cat /sys/firmware/acpi/tables/dynamic/SSDT1 > ssdt1
Please also attach the output of /proc/cpuinfo.
Thanks.
>
> 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]
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-23 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 14:28 No c2-c7 states on core i7 Erik Slagter
2009-11-21 17:45 ` Erik Slagter
2009-11-22 11:46 ` c1/c1e/c3/c6/c7 on linux Erik Slagter
2009-11-23 3:05 ` ykzhao [this message]
2009-11-23 8:52 ` No c2-c7 states on core i7 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=1258945512.3773.33.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox