All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ryan May" <rmay-GrrYUJ3DTa8@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: CPU Performance Management
Date: Tue, 1 Apr 2003 21:33:57 -0600	[thread overview]
Message-ID: <00a201c2f8c8$b2019130$89106144@cyclone> (raw)

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Hi,

I have a Toshiba 2415-s205 with a P4M-2.0GHz and have recently been toying with ACPI support in the linux kernel.  So far, I have gotten two versions running: The 2.5.66 kernel with the 20030328 ACPI patch and the 2.4.20 kernel with the 20021222 ACPI patch.  Neither of the kernels have any other patches applied.

I am happy to see that (with a quick look) many features work well, except for an issue with the 20030328 patch.  When I cat /proc/acpi/processor/CPU0/info I get the following output:

processor id:                      0
acpi id:                              1
bus mastering control:        yes
power management:           yes
throttling control:                no
performance management:  no
limit interface:                    no

Knowing that I have a P4M, I would have expected to have the option of performance management.  Indeed, on the 20021212 patch on a 2.4.20 kernel, I have both performance management and limit interface enabled.  Anyone have any clue what changed to actually disable performance management?

I've tried disassembling and recompiling my DSDT (using iasl 20030228);  It gives me three identical warnings:

Package (0x00) {},
                    ^ Effective AML package length is zero

Could this be my problem?

Any help would be greatly appreciated.

Ryan May

[-- Attachment #2: Type: text/html, Size: 3386 bytes --]

             reply	other threads:[~2003-04-02  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02  3:33 Ryan May [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02  4:27 CPU Performance Management Grover, Andrew

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='00a201c2f8c8$b2019130$89106144@cyclone' \
    --to=rmay-grryuj3dta8@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.