From: Arthur Huillet <arthur.huillet@agoctrl.org>
To: Pavel Troller <patrol@sinus.cz>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Question about AthlonXP on nforce 2 : C2-C3 states
Date: Sun, 5 Feb 2006 16:07:50 +0100 [thread overview]
Message-ID: <20060205160750.4a1c1b3e.arthur.huillet@agoctrl.org> (raw)
In-Reply-To: <20060205143742.GA20815@tangens.sinus.cz>
Hi,
On Sun, 5 Feb 2006 15:37:42 +0100
Pavel Troller <patrol@sinus.cz> wrote:
> If you will see more than 100 in the first line and more than 1000 in the second one, your
> Cx states are blocked by BIOS.
I'm getting 101 and 1001 indeed :
P_LVL2_LAT: 101
P_LVL3_LAT: 1001
Is there no way to tell my BIOS to unblock those states ? I mean, are they blocked for stability
purposes (in what case I assume this is a workaround for a bug in the chipset/CPU/whatever), or are
they just not enabled for an obscure reason ?
Thanks.
--
Greetings,
A.H.
next prev parent reply other threads:[~2006-02-05 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 14:21 Question about AthlonXP on nforce 2 : C2-C3 states Arthur Huillet
2006-02-05 14:37 ` Pavel Troller
2006-02-05 15:07 ` Arthur Huillet [this message]
2006-02-05 15:42 ` Pavel Troller
2006-02-05 15:55 ` Arthur Huillet
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=20060205160750.4a1c1b3e.arthur.huillet@agoctrl.org \
--to=arthur.huillet@agoctrl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=patrol@sinus.cz \
/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