public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Troller <patrol@sinus.cz>
To: Arthur Huillet <arthur.huillet@agoctrl.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Question about AthlonXP on nforce 2 : C2-C3 states
Date: Sun, 5 Feb 2006 15:37:42 +0100	[thread overview]
Message-ID: <20060205143742.GA20815@tangens.sinus.cz> (raw)
In-Reply-To: <20060205152120.1688bd7b.arthur.huillet@agoctrl.org>

> Hello,
> 
> I've recently discovered that my system didn't seem to go into C2/C3 states. In fact, they're not
> even recognized :
> 
> # cat /proc/acpi/processor/CPU0/info 
> processor id:            0
> acpi id:                 0
> bus mastering control:   no
> power management:        no
> throttling control:      no
> limit interface:         no
> 
> # cat /proc/acpi/processor/CPU0/power 
> active state:            C1
> max_cstate:              C8
> bus master activity:     00000000
> states:
>    *C1:                  type[C1] promotion[--] demotion[--] latency[000] usage[00000000]
> 
> Would you happen to know why the Cx states are not seen ? Also, isn't there supposed to be bus
> mastering control available ? 
> My mainboard is a Asus A7N8X rev 1.xx (nforce2).
> The kernels I tried with no success in whatever case are 2.4.29 and 2.6.15.2.
> Unfortunately, google doesn't seem to know much about this problem...
> 
Hi!
  Please try to do something like this:

root@porygon:~/# cat /proc/acpi/fadt |acpitbl |grep P_LVL
P_LVL2_LAT:       190
P_LVL3_LAT:       1900
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. My example is from ASUS A7V8X, which may be similar.

              With regards, Pavel Troller

  reply	other threads:[~2006-02-05 14:38 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 [this message]
2006-02-05 15:07   ` Arthur Huillet
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=20060205143742.GA20815@tangens.sinus.cz \
    --to=patrol@sinus.cz \
    --cc=arthur.huillet@agoctrl.org \
    --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